Data connector defined in native Spring

[Cantor, Scott]

> I can be wrong. In system/conf/global-system.xml, I see :
> 
>     <import resource="../../conf/global.xml" />
>     <import resource="services-system.xml" />
> 
> Where services-system.xml contains '<bean
> id=“shibboleth.AttributeResolverService” …’, so I read that as : beans
> defined in global.xml and services-system.xml are peers (in peer contexts,
> both are children of the same parent).

Beans defined in services-system and global.xml should be in the same context. The beans defined in services-system.xml are (mostly) services, our abstraction that creates a new child Spring context. So the contents of the services are in child contexts, but I believe the parent context of those contexts *is* the root web app context.

Either way, my point is, I would expect a lookup for a bean from the resolver service context to work, but if it's scanning the context for beans of some type, that may not walk up into the parent.

Even if it did, it would be better form in most cases to define it down below, not in global.xml. You don't define things above the scope you need to.

-- Scott