Mostly for Scott: bean load order definition

[Marvin Addison]

>
> 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.
>

It's documented, though not as prominently as you might like:

http://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/beans/factory/support/DefaultListableBeanFactory.html#setAllowBeanDefinitionOverriding-boolean-

That feels like an implementation detail instead of a contract, but as Ian
said it's been that way forever and probably won't change.

My opinion is we should avoid the technique unless it substantially
> improves *user* level configuration of something.
>

Allowing user-space configuration files to contain bean definitions that
override system bean definitions is an incredibly useful feature for
extension. We should support it in some fashion if not use it outright
ourselves.

M
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20151009/edf01925/attachment.html>