THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Spring uses a similar way to map systemIds UIRs to locations on the classpath (spring.schemas files), and that way validates your Spring configuration files. Validation can be disabled (by setting system property spring.validation.mode to VALIDATION_NONE), but the default is to have validation it enabled. This is very useful when you are configuring CXF and not very familiar with CXF's configuration schemas or with Spring itself.What you need to know when writing a valid Spring configuration file is the system IDs for the schema file(s) defining the types that are using in the configuration file.
The table below contains lists the system IDs UIRs for the CXF schema files configuration schemas that you may need to specify in your configuration file, along with their target namespaceSpring 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 these files, as they should be available at their URI. In practice however, only the standard schemas are actually available that way, but 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, to check the content of a schema file, you can use the classpath location in the table below to find the schemas.original version of the schema in the trunk.
Configuration Schemas
URI System ID | Target Namespace | Classpath Resource | Module |
|---|
The following schemas are imported by 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).
...
http://schemas.xmlsoap.org/wsdl/ | http://schemas.xmlsoap.org/wsdl/ | /schemas/wsdl/wsdl.xsd | cxf-common-schemas |
| http://schemas.xmlsoap.org/wsdl/http/ | http://schemas.xmlsoap.org/wsdl/http/ | /schemas/wsdl/http.xsd | cxf-common-schemas |
| http://www.w3.org/2001/xml.xsd | http://www.w3.org/XML/1998/namespace | /schemas/xml.xsd | cxf-rt-ws-policy |
| http://www.w3.org/2006/07/ws-policy.xsd | http://www.w3.org/2006/07/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):
...