|
| |
|
| java.lang.Object
 org.jasig.portal.services.PersonDirectory
| PersonDirectory | | public class PersonDirectory (Code) | | PersonDirectory is a static lookup mechanism for a singleton instance of
IPersonAttributeDao. It is configurable via a
Spring beans.dtd compliant configuration file in the properties directory
called personDirectory.xml (as referenced by applicationContext.xml -
that is, you could choose to declare the underlying IPersonAttributesDao
backing your PersonDirectory directly in applicationContext.xml,
or elsewhere. PersonDirectory looks for an IPersonAttributeDao instance
named 'personAttributeDao'.
This class serves as the lookup mechanism for clients to obtain a reference
to the singleton IPersonAttributeDao instance. Via legacy methods,
PersonDirectory also serves as the interface by which client
code accesses user attributes. These deprecated legacy methods are a facade
to the PersonAttributeDao.
The default configuration of that file implements the legacy behavior of using
the PersonDirs.xml file for configuration. It is expected that PersonDirs.xml
offers the flexibility necessary to support most uPortal installations.
author:
Howard Gilbert
author:
andrew.petro@yale.edu
author:
Eric Dalquist edalquist@unicon.net
version:
$Revision: 35513 $ $Date: 2005-04-06 08:19:32 -0700 (Wed, 06 Apr 2005) $ |
| Field Summary | |
| public static HashSet | propertynames
This instance variable used to contain the set of attributes mapped in
PersonDir.xml. |
| propertynames | | public static HashSet propertynames(Code) | | This instance variable used to contain the set of attributes mapped in
PersonDir.xml. It now is merely an empty Set. It is no longer used by
PersonDirectory and should be removed in a future release.
|
| getPropertyNamesIterator | | public static Iterator getPropertyNamesIterator()(Code) | | This method returns an iterator over the names of attributes. The
method behavior is not well defined because attribute sources may choose
to return different attributes depending upon about whom they are asked.
Therefore, you can only know the attributes for particular users, not the
namespace of all possible attributes.
an iterator over the attribute names declared by the underlyingIPersonAttributeDao instance, if any.IPersonAttributeDao.getPossibleUserAttributeNames |
|
|
|