Grouper Users - Open Discussion List

[Chris Hyzer <>]

Things with the subject API are under your control... :)
Basically it is all interfaces, and there are built-ins, but you can 
customize.

So in your subjects.xml file, you specify the sources, and the 
implementations of the subject api interfaces (probably defaults), and in 
those you could return an object that does a lazy load on the getter of 
certain attributes or whatever, or caches information, etc...

If you need more help, let me know what your subject source is (rdbms or 
ldap), and what exactly you want to cache and what you don't want to cache.

I believe Gary has created a different source adapter which does more caching 
(caches everything?  I don't remember)...

Regards,
Chris


> -----Original Message-----
> From: Martin van Es 
> [mailto:]
> Sent: Thursday, February 12, 2009 2:28 PM
> To: Chris Hyzer
> Cc: Grouper Users Mailing List
> Subject: Re: [grouper-users] Subject external attributes retrieval
> 
> Hi Chris,
> 
> On Thursday 12 February 2009 16:04:42 Chris Hyzer wrote:
> > OK, here is how it works:
> >
> > 1. The default attribute names (comma separated) sent back for each
> request
> > are specified in grouper-ws.properties under the key:
> 
> So do I understand correctly that Grouper will return any arbitrary
> foreign
> attribute given that it's configured under
> ws.subject.result.attribute.names
> (and includeSubjectDetail=true)? Will Grouper allways query the source
> for
> these attributes before returning the result, or may these attributes
> be
> cached at some point in time?
> 
> Grtz
> Martin