...
URI | Target Namespace | Classpath Resource | Module |
---|---|---|---|
/schemas/core.xsd | cxf-rt-core | ||
/schemas/configuration/http-conf.xsd | cxf-rt-transports-http | ||
/schemas/configuration/http-jetty.xsd | cxf-rt-transports-http-jetty | ||
/schemas/configuration/jms.xsd | cxf-rt-transports-jms | ||
/schemas/configuration/security.xsd | cxf-common-schemas | ||
/schemas/configuration/soap.xsd | cxf-rt-bindings-soap | ||
/schemas/jaxws.xsd | cxf-rt-frontend-jaxws | ||
/schemas/simple.xsd | cxf-rt-frontend-simple | ||
/schemas/ws-addr-conf.xsd | cxf-rt-ws-addr | ||
http://cxf.apache.org/schemas/configuration/wsrm-manager-types.xsd | /schemas/configuration/wsrm-manager-types.xsd * | cxf-rt-ws-rm | |
http://cxf.apache.org/schemas/configuration/wsrm-manager.xsd | /schemas/configuration/wsrm-manager.xsd * | cxf-rt-ws-rm |
* wsrm-manager.xsd does an "xsd:include" on wsrm-manager-types.xsd so as they are supposed to be in the same namespace. Most likely, As such, the user just needs to reference wsrm-manager.xsd to use both.
Example
The following is an example of a valid Spring configuration file. Using the table above, there is no magic involved in setting the correct value for the schemaLocation attribute!
...