Attribute resolver dependency question/issue

[Chad La Joie]

On Thu, May 3, 2012 at 1:52 PM, Tom Poage <tfpoage at ucdavis.edu> wrote:
> The definitions are defined in the above order. Is definition order
> important in terms of triggering desired behavior?

No.  The order of plugin resolution is determined by the declaration
of one plugin depending on another.

> Is this simply a case of ambiguity, where the LDAP attribute name is the
> same as the attribute id?

I don't know, what you have right now will result in the following process:
- LDAP data connector will run
- The scripted attribute definition will run, create a new attribute
called "eduPersonAffiliation" and give it a value of "member"
- The Scoped attribute definition will run and pull in the values for
the "eduPersonAffiliation" (exact match on that name) LDAP attribute
and the "eduPersonAffiliation" attribute from the scripted data
connector and append the ucdavis.edu scope to all of them.

> Lastly, the wiki page above indicates id="..." instead of ref="..." for
> resolver:Dependency. I don't see 'id' in the XSD (or perhaps I'm not
> reading it correctly).

That was a typo and has now been fixed.

-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered