SVN resources for Services. SVN resources for Metadata

[Rod Widdowson]

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

So, for example, the following plugs into a standard config:

    <util:list id="shibboleth.MetadataResolverResources">
        <value>%{idp.home}/conf/metadata-providers.xml</value>
        <value>%{idp.home}/system/conf/metadata-providers-system.xml</value>
    </util:list>

    <util:list id ="shibboleth.AttributeResolverResources">
        <metadata:MetadataResource xsi:type="resource:SVNResource" 
                      resourceFile="attribute-resolver.xml"
 
repositoryURL="https://svn.shibboleth.net/java-identity-provider/trunk/idp-c
onf/src/main/resources/conf"
                      workingCopyDirectory="..." 
                      revision="7234"/>
    </util:list>

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>

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

/R