activationConditionRef problem

[Cantor, Scott]

On 7/11/15, 1:02 PM, "dev on behalf of Rod Widdowson" <dev-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:
>
>I always assumed that that was because the RTL had the symbols stripped (or
>perhaps because that stuff was native).  But there again perhaps I'm too
>much tied to thinking about COFF and ELF...

No, Java's refelection support means all that stuff has to be kept.

>Either way I have confirmed that adding a new constructor which takes a
>single parameter of the String will also cause c:_0="entityID" to 'do the
>right thing'.

That's true, I guess. In this particular case it's probably ok to circumvent the ability to specify "true" and "false" because hardwiring that into a condition like this probably doesn't serve much purpose, but once in a while for debugging you might want to temporarily hardwire a condition to true or false, so that's why I was a little hesitant to break that.

The main use case for having that String->Predicate converter was for things like the signing or encryption flags on the profiles, to make it easy to set them on or off.

-- Scott