Mostly for Scott: bean load order definition

[Cantor, Scott]

On 10/9/15, 9:20 AM, "dev on behalf of Rod Widdowson" <dev-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:



>I see that in R7721 we introduce a bean (shibboleth.CustomViewContext) at
>the very top of global-system.xml so that a bean of that name always exists.
>Then we rely on someone redeclaring it global.xml to be what they really
>want.

I'll see if I can work around it, but I was aware I did it. I thought that they did document "last one wins" somewhere, but if not I agree I should find another way.

The reason "last one wins" is safe here is that global-system is the top file, so anything else by definition is "last". I wouldn't ever do this between two files loaded elsewhere that don't have an explicit ordering. In other words, declaring in a file that itself imports another file where the override would be is "safe".

I've done it sparingly, only when it was apparently not possible to avoid declaring a bean. Usually I try and use getObject conditionally. I was having trouble getting that to work in the flow files.

-- Scott