SVN resources for Services. SVN resources for Metadata

[Rod Widdowson]

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

True, on both counts.  

I'll see what I can do about documenting two of the metadata resources (SVN
and Classpath).

I'm currently not planning documenting the other two (HTTP and
FilebackedHTTP) which are there for legacy reasons, but that segues into
another meta question about documentation.

I have not been documenting things which are there purely for V2
compatibility (like disregardSslCertificate for the MetadataProviders), do
we feel that this is correct  or should we document it and say "Deprecated,
use disregardTLSCertificate)

/R