...
The basic class for a uPotal user is an implementation of the IPerson object. The uPortal Person Directory Service is used to populate and retrieve user attributes. Person Directory is maintained as a separate source project PersonDirectory. uPortal 3.2 provides the single class, PersonDirectory, to obtain an instance of IPersonAttributeDao. IPersonAttributeDao is configured by Spring to acquire attributes for a personThis class is currently deprecated and will no longer be needed in a future version of uPortal that is entirely Spring configured. Attributes can be acquired from multiple sources via LDAP, JDBC or other sources as required.
...
Spring and PersonDirectory
PersonDirectory is implemented using Spring. Currently a Spring beans.dtd-compliant XML file named personDirectoryContext.xml declares the configuration of an instance of IPersonAttributeDao. The class PersonDirectory delegates to this Spring-configured IPersonAttributeDao instance to actually implement the PersonDirectory behavior. PersonDirectory uses PortalApplicationContextFacade to access the the uPortal Spring application context.
JDBC Example
For examples, visit the page dedicated to JDBC User Attribute Sources.
LDAP example
For examples, visit the page dedicated to LDAP User Attribute Sources.
Request Attribute Filter Example
...
| Warning | ||
|---|---|---|
| ||
Although not recommended it is possible to change the class name in the personDirectory.xml beans declaration to be a custom class of your choice, so long as it implements IPersonAttributeDao. You could then write a custom implementation that does exactly the queries, caching, and any other behavior you need. |