Create and use some wrapper around javax.xml.validation.Schema [SWS-179]

[gregturn]

Martin Vanek opened SWS-179 and commented

Many spring-ws components use Schema, but only via org.springframework.core.io.Resource which enforces reloading an recreating. Schema creation is very expensive operation and therefore should be better to have some component holding schema (maybe ?org.springframework.xml.validation.XmlValidator?) and use this component as alternative schema parameter for Schema using components.

---

Affects: 1.0

Issue Links:

• add support for imported xsd in static wsdl as well as xsd's that import other xsd's [SWS-281] #438 add support for imported xsd in static wsdl as well as xsd's that import other xsd's

• Support XsdSchema in AbstractValidatingInterceptor [SWS-304] #460 Support XsdSchema in AbstractValidatingInterceptor

• Enable MessageDispatcherServlet to serve included xml schemas [SWS-250] #405 Enable MessageDispatcherServlet to serve included xml schemas

1 votes, 1 watchers

[gregturn]

Arjen Poutsma commented

Frameworks we could use for this:

http://ws.apache.org/commons/XmlSchema/index.html
https://xsom.dev.java.net/

[gregturn]

Aleksei Valikov commented

I'd opt to XSOM since this would allow easier integration with XJC and JAXB RI.

I'm not quite sure which "schema-using components" are meant though.

[gregturn]

Martin Vanek commented

I meant especially org.springframework.oxm.jaxb.Jaxb2Marshaller and org.springframework.xml.validation.XmlValidator. They are both loading schema through spring Resource interface so reusing one loaded schema instance is impossibe.

[gregturn]

Arjen Poutsma commented

XSOM is Java 5 only, while Apache XmlSchema is Java 1.4 and higher. So I prefer XmlSchema.

[gregturn]

Arjen Poutsma commented

Additionally, XSOM is unsuitable, because it fails to handle the more complex include/import scenario's.

[gregturn]

Arjen Poutsma commented

Closing issues for 1.5.