> <bean id="mergedPersonAttributeDao"
> class="org.jasig.services.persondir.support.MergingPersonAttributeDaoImpl">
> <property name="personAttributeDaos">
> <list>
> <ref bean="attributeRepository" />
> </list>
> </property>

I believe this is wrong.  The top-most attribute repository bean must
be called attributeRepository, so you'd want
MergingPersonAttributeDaoImpl to have the name "attributeRepository"
and the delegated attribute repository to have another name.  We do
something very similar in our environment, and this strategy works
well for us.

> All attributes have been allowed in service management but still the
> attributes are not released.

I must admit I'm doubtful the bean naming issue I described above is
preventing attributes from being released, but let's fix that and see
where it gets us.

M

-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to