Kris, [ For future releases is the entire org.jasig.portal.services.persondir.support package going to be removed and a dependency on the person-directory project created?
] Loosely, yes. Speaking abstractly: It is likely the case that there will still be a need for uPortal-specific classes implementing these APIs. For instance, a LegacyPersonAttributeDao that parses the legacy PersonDirs.xml and implements the behavior defined in that file is one way to smooth the path for upgraders. Such an implementation would be uPortal-specific and still live in the uPortal source tree. So it may not be the case that uPortal divests entirely of core related to this and *just* adds the dependency. Speaking concretely: I note that the trunk depends on person directory standalone API and .jar https://www.ja-sig.org/svn/up2/trunk/uportal-impl/pom.xml and I notice that the code package you reference is gone: https://www.ja-sig.org/svn/up2/trunk/uportal-impl/src/main/java/org/jasig/portal/services/ So uPortal 3.0 and later will be using the more modern person attributes APIs. Andrew Kris Easter wrote: > We're working on implementing 2.6.1 and it doesn't look like > MultiRowJdbcPersonAttributeDao is a simple swap out for the current > JdbcPersonAttributeDaoImpl (a class cast exception is thrown on the > IPerson object at some point). > > For future releases is the entire > org.jasig.portal.services.persondir.support package going to be removed > and a dependency on the person-directory project created? > > Thanks, > Kris > > On Tue, 2008-03-04 at 11:28 -0600, Eric Dalquist wrote: > >> More specifically MultiRowJdbcPersonAttributeDao is the class you're >> looking for in the stand-alone project. >> >> -Eric >> >> Eric Dalquist wrote: >> >>> What version of uPortal are you using? Person Directory has been >>> rolled out into a stand-alone project and that project has a >>> mult-valued user attribute support. Depending on your version of >>> uPortal you may be able to use this stand-alone person directory code. >>> >>> http://developer.ja-sig.org/projects/person-directory/1.0.0/apidocs/index.html >>> >>> >>> >>> -Eric >>> >>> >>> >>> Kris Easter wrote: >>> >>>> 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
