Done. Also, the handler adapter is integrated in the MessageDispatcherServlet, so that it automatically exposes all XsdSchema instances in the application context, under $
.xsd. This is consistent with the WSDL exposing behavior.
I decided not to add any transformation logic for now, because I couldn't think of a solution which would work in all situations (absolute reference URI's, XSDs contained in jars, etc). Subclasses can add this behavior though, in the getSchemaSource() template method.