activationConditionRef problem

[Cantor, Scott]

On 7/9/15, 3:45 PM, "users on behalf of Liam Hoekenga" <users-bounces at shibboleth.net on behalf of liamr at umich.edu> wrote:

>I got it working with
>
>    <bean id="ExampleOrgPredicate" parent="shibboleth.Conditions.RelyingPartyId" c:candidates="#{ 'https://shib-sp-test.www.umich.edu/shibboleth' }"/>

You're not really buying anything wrapping the string that way, c:candidates="foo" alone should work. But yes, that will force the right constructor to get used, sometimes at least.

The reality is that the parameter is a list of strings and the prudent thing is to give it that. #{'foo'} is just a string. #{{'foo'}} is a list of strings, size 1.

>I'm still learning about Spring.  Are c:_0 and c:candidates somewhat equivalent?  Should c:_0 access the zero slot in the c:candidates structure?

No, the 0 is the index of the constructor argument you're supplying to the class you're building. Saying c:candidates tells it to look for a constructor with a parameter with that name, which the right constructor does have and the wrong constructor it was using before doesn't.

I think we can fix the behavior so it doesn't silently behave like this one way or the other, I asked Rod to file a bug so we can study the tradeoffs.

-- Scott