activationConditionRef problem

[Rod Widdowson]

> >
> >Any ideas or shall I start spelunking?
> 
> I answered there before I saw this thread. Just weird precedence for the
> converters, I don't think there's a lot we can do about it. Maybe if we do
> some kind of conditional conversion, but IIRC the "conditional" check on
the
> converters doesn't have access to the value it's going to convert, so
there's
> no way to check for true and false and ignore other values.

Ah, so "https://whatever" becomes "Boolean.false" becomes
"Predicate.ALWAYS_FALSE"?

Given that the c_0="{{'foo'}}" is easy I'd be inclined to leave this as is.
But if it is liable to trick more people perhaps we should add a third
constructor which takes a String; that would override all the conversions.
This means that c_0="true" would stop falling into the predicate case, but
I'm not sure that that is obvious in this case.

R