It appears that the JdbcPersonAttributeDaoImpl class expects a SQL query that returns a single row per user. We are interested in returning multiple rows from a SQL query in the same way multiple values per attribute are now returned and handled from LDAP queries.
As a proof of concept I changed the JdbcPersonAttributeDaoImpl class to handle multiple rows but I'm wondering if there are unintended consequences to doing so that I'm not familiar with? If there are no negatives is this something that could be included in the framework going forward? Thanks, Kris -- Join your friends and colleagues at JA-SIG 2008 - "Higher Education Solutions: The Community Source Way!" April 27th - 30th, 2008 in St. Paul, Minnesota USA Featuring CAS, DSpace, Fedora, Fluid, Internet2, Kuali, Sakai, uPortal, and more! Information/Registration at: http://www.ja-sig.org/conferences/08spring/index.html You are currently subscribed to [email protected] as: [EMAIL PROTECTED] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/uportal-dev
