Quick thought about XML vs annotations for Spring wiring

[Cantor, Scott]

On 9/24/15, 10:34 AM, "dev on behalf of Misagh Moayyed" <dev-bounces at shibboleth.net on behalf of mmoayyed at unicon.net> wrote:
>
>Yes, exactly. Thanks for bring this up. If you are just extending the IdP
>platform, there needs to be a way to insert beans into the context without
>actually touching system files. Otherwise, upgrades would become very
>painful. Given the current IdP config architecture, I'd be inclined to
>simply include a template XML config file that is totally empty, into the
>context which is then decorated with all the right spring namespaces.
>Then, the IdP would load this file in such a way that beans get inserted
>into the context as the last step, which has the additional advantage of
>overriding other bean configuration spread in various other files.
>
>Overlay-style, as it were.

We mostly do but the MVC and webflow files are being loaded by the IdP servlet context and not globally, which I forgot, so we're missing an include.

I'm not too keen on relying on bean overrides, though, just feels brittle. Some of that's unavoidable because MVC config isn't that clean, but for most of our components we use other techniques to handle it.

-- Scott