Review infrastructure setup for schemas

[bclozel]

While updating the "Producing a SOAP service" guide, I noticed that ".xsd" and ".wsdl" files are scanned in a configurable location. Beans are created with their names derived from the file name (typically, SimpleXsdSchema and DefaultWsdl11Definition beans).

If a SimpleXsdSchema is created, developers must expand it and instantiate a new DefaultWsdl11Definition bean to expose the WSDL service definition. Again, bean names are important because they are used to map the service definitions in the dispatcher.

This issue is about reviewing the current infrastructure setup and consider whether alternative designs are possible.

[snicoll]

These beans are actually scanned by the Spring Boot auto-configuration, but it is Spring WS that makes the bean name magic, indeed. We should offer a way to return the name of the definition and that should happen here.

[snicoll]

One option was to create the concept of a registry that's a glorified view of a name to definition map. I didn't go down that route as the definitions are implementing framework callbacks and creating them manually means we have to honour those callbacks. I've added the notion of a name for now, that doesn't force users to name their bean a certain way as long as the name is provided on the definition.