Porting advanced v2 resolver config to v3

[Marvin Addison]

> I just added a trace() to both of the statement builders that would prove
> what we already assume, that uid isn't in the dependency set.
>

I updated to last night's snapshot to pull in additional logging and
noticed the following entry in subsequent testing:

2015-02-11 09:31:49,946 - TRACE
[net.shibboleth.idp.attribute.resolver.dc.impl.AbstractSearchDataConnector:179]
- Data Connector 'edEntitlement': Cache found, resolved attributes null
using cache com.google.common.cache.LocalCache$LocalManualCache at 579736d4

I have a cache bean defined in the Spring XML file sourced for _each_ data
connector, the dependency and the dependent, and these are separate bean
instances judging from the following entry, which appears earlier in the
log for the same request:

2015-02-11 09:31:49,729 - TRACE
[net.shibboleth.idp.attribute.resolver.dc.impl.AbstractSearchDataConnector:179]
- Data Connector 'edPerson': Cache found, resolved attributes null using
cache com.google.common.cache.LocalCache$LocalManualCache at 1ab0b267

Shouldn't I be using a shared cache? I have no idea how to do that,
however, unless there's a shibboleth.Cache bean in the root context that I
missed.

M <users-unsubscribe at shibboleth.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20150211/7ca23afe/attachment.html