Missing unmodifiable exception in *FlowDescriptor setActivationCondition() ?

[Tom Zeller]

On Mon, Sep 8, 2014 at 7:38 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 9/8/14, 8:19 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
>>
>>We have a problem also in the flow tests in idp-conf. I'm overriding an
>>activation condition for the c14n flows to avoid having to put things we
>>don't want into the default files.
>>
>>I don't know how to fix that, I'm not clear on how to alter bean
>>definitions in the tests.
>
> I don't know if there's a way to do it in code, but I guess at the top
> level, I can override beans in the config files using test-beans.xml, so
> that seems to fix it.

I guess test-beans.xml and override-beans.xml are a little redundant,
but it's not a big deal. The way to override beans in code was to get
the application context from the flow definition from the flow
executor, assuming the flow ID is known. But doing that in XML might
be better anyway.