Metadata Generation

[Rod Widdowson]

> Right. So my question was, does it barf if there's no metadata defined at
> all, just an empty Spring file loaded into the service? 

The answer is - no.  What happens is that we die horribly inside Spring when
we say "load this bean file", this in turn is provoked by Xerces having been
called to do a parse().

However what I have confirmed as working (and put in a test to prove) is an
empty ChainingMetadataProvider.   I'm guessing that in many cases people
will want to end up having a chain in there and in the other cases having a
singleton chain will cost near to nothing, and for those that want to save
the tens of bytes and thousands of picoseconds can reconfigure with their
singleton provider as the top level element.

Shipping with an empty Chain means that we can add examples (commented out)
into the distribution of loading from a file and loading from an HTTP
provider.

I'll see whether I can persuade the test framework to accept having the
current configuration as a test resource and the proper demo as the real
resource.

Rod