SOAP over JMS

In this recipe, we will implement reliable SOAP communication over JMS and not over HTTP. The only difference is that your request and response will be published on a queue. This way the request can't be lost (when it has JMS persistence with XA/QoS). The response will also be published on the queue and the client can consume this response.

Getting ready

For this recipe, we will use an OSB project with a proxy service that is based on a WSDL with a synchronous request/response operation. The SOAP message will be sent over JMS instead of HTTP. JDeveloper will be used to generate a test client:

You can import the OSB project into Eclipse OEPE from \chapter-10\getting-ready\sending-soap-over-jms.

How to do it...

First we will need to change the proxy service to use the JMS instead of the HTTP transport. In Eclipse OEPE, perform the following steps:

1. Open the SoapOverJMS proxy service.

2. Click on the Transport tab.

3. Choose jms in the Protocol field.

4. The Endpoint URI must use a XA Connection...