Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

URI

Target Namespace

Classpath Resource

Module

http://cxf.apache.org/schemas/core.xsd

http://cxf.apache.org/core

/schemas/core.xsd

cxf-rt-core

http://cxf.apache.org/schemas/configuration/http-conf.xsd

http://cxf.apache.org/transports/http/configuration

/schemas/configuration/http-conf.xsd

cxf-rt-transports-http

http://cxf.apache.org/schemas/configuration/http-jetty.xsd

http://cxf.apache.org/transport/http-jetty/configuration

/schemas/configuration/http-jetty.xsd

cxf-rt-transports-http-jetty

http://cxf.apache.org/schemas/configuration/jms.xsd

http://cxf.apache.org/transports/jms

/schemas/configuration/jms.xsd

cxf-rt-transports-jms

http://cxf.apache.org/schemas/configuration/security.xsd

http://cxf.apache.org/configuration/security

/schemas/configuration/security.xsd

cxf-common-schemas

http://cxf.apache.org/schemas/configuration/soap.xsd

http://cxf.apache.org/bindings/soap

/schemas/configuration/soap.xsd

cxf-rt-bindings-soap

http://cxf.apache.org/schemas/jaxws.xsd

http://cxf.apache.org/jaxws

/schemas/jaxws.xsd

cxf-rt-frontend-jaxws

http://cxf.apache.org/schemas/simple.xsd

http://cxf.apache.org/simple

/schemas/simple.xsd

cxf-rt-frontend-simple

http://cxf.apache.org/schemas/ws-addr-conf.xsd

http://cxf.apache.org/ws/addressing

/schemas/ws-addr-conf.xsd

cxf-rt-ws-addr

http://cxf.apache.org/schemas/configuration/wsrm-manager-types.xsd

http://cxf.apache.org/ws/rm/manager

/schemas/configuration/wsrm-manager-types.xsd *

cxf-rt-ws-rm

http://cxf.apache.org/schemas/configuration/wsrm-manager.xsd

http://cxf.apache.org/ws/rm/manager

/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!

...