Page History

...

CXF uses XML schemas extensively in the runtime: Its core includes the JAXB mappings of standard schemas such as http://schemas.xmlsoap.org/wsdl/ and http://www.w3.org/2006/03/addressing/ws-addr.xsd. CXF also defines its own schemas for WSDL extensions such as the jms-address element in namespace http://cxf.apache.org/transports/jms, and schemas for both Spring and Blueprint (OSGi) configuration, for example the http://cxf.apache.org/jaxws and http://cxf.apache.org/blueprint/jaxws namespace namespaces.

To avoid accessing resources over the network during a build, CXF maintains local copies of these schemas. Logically however, third party as well as CXF schemas , are as well as the CXF schemas, are referred to by their public URIs in schemaLocation attributes and similar places. The CXF code generators use catalog files to map them to their actual location in the trunk, see the pom.xml file in the api module for an example.

Spring uses a similar way to map URIs to locations on the classpath (spring.schemas files), and that way validates your Spring configuration filesNote if you're using Spring it will validate your Spring configuration files, using information in each JAR's META-INF/spring.schemas file (an example here). Validation is extremely helpful in diagnosing errors in CXF configurations, but it is also very expensive at runtime. Once you have got your application working, you can disable validation by setting a system property: org.apache.cxf.spring.validation.mode (in 2.1) or spring.validation.mode (in 2.0.x). Set it as follows to disable validation: -Dorg.apache.spring.validation.mode=VALIDATION_NONE

The table below lists includes the URIs for the CXF configuration schemas that you need to specify in your Spring configuration file's schemaLocation attribute so that Spring's validating parse parser can validate the file.
In theory you need not be concerned with the actual location of the files: Spring knows about can normally detect their location on from the classpath. And if you want to check the content of a schema file (in a binary distribution), you should be able to do so using its URI. At the moment this is not possible, however CXF aims at publishing its schemas in the future. In the meantime, you can You can also use the classpath location in the table below to find the original version of the schema in the trunk.

Configuration Schemas common to both Spring and Blueprint

* 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

Blueprint-only Schemas

* 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.

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 (actually, it'd be cool if someone wrote a CatalogResolver based on the URI - classpath location mappings that already exist and get the CXF tools and/or xjc to use it).

...