Elliot,
Thanks - I followed all that logic through. But ultimately it would
look like *somewhere* in the code for the container it would *ask*
for the attribute "userAttributeService" and then cast that to
UserInfoAttributesService and then *do* something with the service to
get the user attributes.
But alas, I cannot find any such code in the container.
/Chuck
On Feb 26, 2007, at 11:05 PM, Elliot Metsger wrote:
Chuck,
Services are wired up using the Pluto Portal's
pluto-portal-driver-services-config.xml.
Around line 80 you'll see a commented out bean for the UserAttributes
service.
BUT, o.a.p.driver.config.impl.DriverConfigurationImpl doesn't have a
setter for that service, so you'll need to extend
DriverConfigurationImpl, and add the setter method for the
UserAttributes service.
Then you need to update pluto-portal-driver-services-config.xml to use
*your* DriverConfigurationImpl with the uncommented
userAttributesService property reference.
I think that should work :)
HTH,
Elliot
Sent from webmail (apologies for the poor quoting)
Charles Severance <[EMAIL PROTECTED]> 02/26/07 10:08 PM >>>
I want to set the User Info Attributes pulling information from
Sakai's UserDirectoryServices into Pluto 1.1.
I know that I have to provide an implementation for
org.apache.pluto.spi.optional.UserInfoAttributesService;
And I can even see some sample source code here:
pluto-portal-driver-impl/src/main/java/org/apache/pluto/driver/
services/impl/UserInfoAttributesServiceImpl.java
What I cannot for the life of me figure out where the impl is wired
into the Pluto container or how the container "notices" that such an
implementation is to be used.
I am looking for properties file or something and not finding it. I
am guessing that it is some clever magic I just cannot fathom.
/Chuck