...
Configuration Schemas common to both Spring and Blueprint
URI | Target Namespace | Classpath Resource | Module |
|---|---|---|---|
/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-core | ||
/schemas/configuration/soap.xsd | cxf-rt-bindings-soap | ||
/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 | |
/schemas/clustering.xsd | cxf-rt-features-clustering |
* wsrm-manager.xsd does an "xsd:include" on wsrm-manager-types.xsd as they are in the same namespace. As such, the user just needs to reference wsrm-manager.xsd to use both.
Spring-only Schemas
URI | Target Namespace | Classpath Resource | Module |
|---|---|---|---|
/schemas/core.xsd | cxf-core | ||
/schemas/jaxrs.xsd | cxf-rt-frontend-jaxrs | ||
/schemas/jaxws.xsd | cxf-rt-frontend-jaxws | ||
/schemas/policy.xsd | cxf-rt-ws-policy | ||
/schemas/simple.xsd | cxf-rt-frontend-simple |
Blueprint-only Schemas
URI | Target Namespace | Classpath Resource | Module |
|---|---|---|---|
/schemas/blueprint/core.xsd | cxf-core | ||
/schemas/blueprint/jaxrs.xsd | cxf-rt-frontend-jaxrs | ||
/schemas/blueprint/jaxws.xsd | cxf-rt-frontend-jaxws | ||
/schemas/blueprint/policy.xsd | cxf-rt-ws-policy | ||
/schemas/blueprint/simple.xsd | cxf-rt-frontend-simple |
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!
...
The following schemas are imported by one or more of the schemas above, directly or indirectly. You may also find their classpath locations useful when you import or include any of the schemas below in your own schema, and want to know hpw you can access them locally.
URI | Target Namespace | Classpath Resource | Module |
|---|---|---|---|
/schemas/configuration/cxf-beans.xsd | cxf-core | ||
/schemas/wsdl/http-conf.xsd | cxf-rt-transports-http | ||
/schemas/wsdl/jms.xsd | cxf-rt-transports-jms | ||
/schemas/wsdl/spec/jms-spec-wsdl.xsd | cxf-rt-transports-jms | ||
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd | http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd | /schemas/oasis-200401-wss-wssecurity-secext-1.0.xsd | cxf-rt-ws-policy |
http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd | http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd | /schemas/oasis-200401-wss-wssecurity-utility-1.0.xsd | cxf-rt-ws-policy |
/schemas/wsdl/addressing.xsd | cxf-core | ||
/schemas/ws-policy-200409.xsd | cxf-rt-ws-rm | ||
/schemas/configuration/wsrm-policy.xsd | cxf-rt-ws-rm | ||
/schemas/wsdl/wsdl.xsd | cxf-core | ||
/schemas/wsdl/http.xsd | cxf-core | ||
/schemas/xml.xsd | cxf-rt-ws-policy | ||
/schemas/ws-policy-200607.xsd | cxf-rt-ws-policy |
Note for Developers: If you define your own configuration schema, place it in the schemas subdirectory of the resources directory, then combine http://cxf.apache.org/ and the path of the schema relative to the resources directory to form the system ID, and make the latter known to Spring by adding a line similar to the following to the spring.schemas file in your module's META-INF directory (note the escaped : character):
...