Missing unmodifiable exception in *FlowDescriptor setActivationCondition() ?

[Tom Zeller]

On Tue, Sep 9, 2014 at 9:08 AM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> On 9/9/14, 10:04 AM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:
>>
>>I guess test-beans.xml and override-beans.xml are a little redundant,
>>but it's not a big deal.
>
> The testbed uses test-beans.xml as well, in the non-IdP portions. So
> putting things there breaks the testbed if they override the configuration
> because they'll typically pull in beans that aren't part of the other
> Spring contexts in the testbed.

Oh, okay, I didn't remember that.

>>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.
>
> I can get the beans fine, but I can't change them after they're already
> initialized.

Right, I was thinking just add a new bean to the application context
with the same ID, but apparently that's not exactly as
straightforward, or even possible, as I was thinking it was.