[EXT] idp 5.2.0 upgrade fails - org.opensaml.core.xml.config.XMLObjectProviderRegistry was unavailable

[Scott Cantor]

> I think I'll stop trying to stick it in random places for now <sigh>.

Nothing in the global context is going to change anything, unless it can live inside a resource loaded into a service. I must have a requirement of some sort to depend on a bean that it isn't being wired up to depend on if it's defined globally.

I can't fathom what it has to do with the thing it's breaking, but I don't know what the code looks like without reading it. That doesn't obviously have anything to do with the code that's causing trouble.

If it worked before, then the issue is Spring 7, it's changing the order of bean creation and so there's a depends-on attribute needed in a bean somewhere to force the righr creation order to happen.

So yes, likely a bug strictly speaking unless the intention is to define that inside a service somewhere.

> Seems you can :). Is there a prize for finding the most obscure bugs you
> didn't think were possible ;)?

That depends on where the bean is actually meant to be defined. There are lots of thiings that can't be in the root context for various reasons, but I don't know anything about that one.

As a workaround, adding depends-on="shibboleth.OpenSAMLConfig" might fix it, and that could ultimately go into the parent bean to fix it.

-- Scott