+

Search Tips   |   Advanced Search

Linking a WSIF service to a JMS-provided service


The JMS providers enable a WSIF service to be invoked through either SOAP over JMS, or native JMS. Add Web Services Description Language (WSDL) extensions to the Web service WSDL file so that the service can use the JMS providers.

The JMS is an API for transport technology. The mapping to a JMS destination is defined during deployment and maintained by the container.

The JMS destination endpoint for a Web service can be realized in any of the following ways:

The JMS destination endpoint must respect the interaction model expected by the client and defined by the WSDL. It must return a response if one is required.

When the JMS destination endpoint creates the JMS response message the following rules must be followed:

The client does not see any of these headers. The container receives the JMS message and (for SOAP over JMS) removes the SOAP message to send to the client.

To link a WSIF service to a JMS-provided service, use the information and code examples given in the following topics:

 


Example: Writing the WSDL extension that enables the WSIF service to access a SOAP over JMS service
Example: Writing the WSDL extensions that enable the WSIF service to access an underlying service at a JMS destination
Enable a WSIF client to invoke a Web service through JMS
JMS message header: The TimeToLive property reference

 

Related tasks


Linking a WSIF service to a SOAP over HTTP service
Linking a WSIF service to the underlying implementation of the service

 

Related


Example: Writing the WSDL extension that enables the WSIF service to invoke a method on a local Java object
Example: Writing the WSDL extension that enables the WSIF service to invoke an enterprise bean