Use of Schemas and Namespaces

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 Spring configuration, for example the http://cxf.apache.org/jaxws namespace.

...

Spring uses a similar way to map URIs to locations on the classpath (spring.schemas files), and that way validates your Spring configuration files. 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 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 can validate the file.
In theory you need not be concerned with the actual location of the files: Spring knows about their location on 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 use the classpath location in the table below to find the original version of the schema in the trunk.

...