LibraryToggle FramesPrintFeedback

The SOAP over JMS protocol is defined by the World Wide Web Consortium(W3C) as a way of providing a more reliable transport layer to the customary SOAP/HTTP protocol used by most services. The Fuse Services Framework implementation is fully compliant with the specification and should be compatible with any framework that is also compliant.

This transport uses JNDI to find the JMS destinations. When an operation is invoked, the request is packaged as a SOAP message and sent in the body of a JMS message to the specified destination.

To use the SOAP/JMS transport:

  1. Specify that the transport type is SOAP/JMS.

  2. Specify the target destination using a JMS URI.

  3. Optionally, configure the JNDI connection.

  4. Optionally, add additional JMS configuration.

You specify the address of the JMS target destination when specifying the WSDL port for the endpoint. The address specification for a SOAP/JMS endpoint uses the same soap:address element and attribute as a SOAP/HTTP endpoint. The difference is the address specification. JMS endpoints use a JMS URI as defined in the URI Scheme for JMS 1.0. Example 9.2 shows the syntax for a JMS URI.


Table 9.1 describes the available variants for the JMS URI.


The options portion of a JMS URI are used to configure the transport and are discussed in JMS URIs.

Example 9.3 shows the WSDL port entry for a SOAP/JMS endpoint whose target destination is looked up using JNDI.


For working with SOAP/JMS services in Java see Using SOAP over JMS in Developing Applications Using JAX-WS.

Comments powered by Disqus