Over a million developers have joined DZone.

Respond to the Client After Sending the SOAP Request to the JMS Queue

DZone's Guide to

Respond to the Client After Sending the SOAP Request to the JMS Queue

Free Resource

Are your API program basics covered? Read the 5 Pillars of Full Lifecycle API Management eBook

This can be achieved with the following configuration.

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://ws.apache.org/ns/synapse">
   <registry provider="org.wso2.carbon.mediation.registry.WSO2Registry">
      <parameter name="cachableDuration">15000</parameter>
   <proxy name="StockQuoteProxy"
            <property name="OUT_ONLY" value="true"/>
                     <address uri="http://localhost:9000/services/SimpleStockQuoteService"/>
               <target sequence="test"/>
   <sequence name="test">
            <ns:a xmlns:ns="http://services.samples">
      <property name="HTTP_SC" value="202" scope="axis2"/>
      <header name="To" action="remove"/>
      <property name="RESPONSE" value="true"/>
   <sequence name="fault">
      <log level="full">
         <property name="MESSAGE" value="Executing default 'fault' sequence"/>
         <property name="ERROR_CODE" expression="get-property('ERROR_CODE')"/>
         <property name="ERROR_MESSAGE" expression="get-property('ERROR_MESSAGE')"/>
   <sequence name="main">
         <log level="full"/>
         <filter source="get-property('To')" regex="http://localhost:9000.*">
      <description>The main sequence for the message mediation</description>

Please replace the following line according to your end point.
" <address uri="http://localhost:9000/services/SimpleStockQuoteService"/> "

Establish API creation, publishing and discovery as a master practice with the API Management Playbook.


Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}