SVN resources for Services. SVN resources for Metadata

[Cantor, Scott]

On 4/8/15, 3:50 PM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:



>I just discovered, slightly to my horror, that mixed mode (native/custom)
>bean configuration actually works.

I guess that makes sense. I assume Spring just loads every spring.handlers 
file it finds and registers every namespace. I guess that's probably 
something we can eventually take advantage of in specific cases. I hadn't 
considered that working.

>Should I assume that this is something we won't be documenting? Or does 
>the
>'ease' provide any value?  In that case we should perhaps rename from
><metadata:MetadataResource>

Well, yeah, I wouldn't think we'd document it like that.

>My instinct is that the change would be better the other way around and 
>that
>we (I really) missed a trick on not looping around on the syntax of the
>ResourceBackedMetadataProvider before we shipped V3.0.
>
>I propose that we deprecate the entire <resource:> syntax and instead 
>allow
>for externally specified beans to be plugged into the
>ResourceBackedMetadataProvider.
>
>If we then only documented the external bean mechanism we could then share
>common configuration resources specified under
>https://wiki.shibboleth.net/confluence/display/IDP30/ReloadableServices

I don't know about the deprecate part. Sort of keeps coming back to my 
issue with locality of reference. I like having the ability to inject 
beans anywhere we can do it, but I don't think most people will typically 
like having to go create separate definitions for things. I wish we had 
been able to come up with a way of embedding <beans>.

-- Scott