MuleSoft Application Development With JMS Queue Explained: Part Three

Introduction

In my last post, I covered the configuration of request-reply pattern. This can also achieve by using the request-reply scope

The Configuration

The XML file is listed as the following:

?

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

<!--xml version="1.0" encoding="UTF-8"?-->   <mule xmlns:dw="http://www.mulesoft.org/schema/mule/ee/dw" xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns:jms="http://www.mulesoft.org/schema/mule/jms" xmlns:tracking="http://www.mulesoft.org/schema/mule/ee/tracking" xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:spring="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemalocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd http://www.mulesoft.org/schema/mule/jms http://www.mulesoft.org/schema/mule/jms/current/mule-jms.xsd http://www.mulesoft.org/schema/mule/ee/tracking http://www.mulesoft.org/schema/mule/ee/tracking/current/mule-tracking-ee.xsd http://www.mulesoft.org/schema/mule/ee/dw http://www.mulesoft.org/schema/mule/ee/dw/current/dw.xsd">     <flow name="request-replyFlow">         <http:listener config-ref="HTTP_Listener_Configuration" path="/jms/reply" doc:name="HTTP">         <dw:transform-message doc:name="Json To Java">             <dw:set-payload><!--[CDATA[%dw 1.0 %output application/java --- payload]]--></dw:set-payload>         </dw:transform-message>         <set-property propertyname="MULE_CORRELATION_ID" value="#[message.sku]" doc:name="Set Correlation ID">         <request-reply doc:name="Request-Reply">             <jms:outbound-endpoint queue="order.request" connector-ref="Active_MQ" doc:name="JMS">             <jms:inbound-endpoint queue="order.reply" connector-ref="Active_MQ" doc:name="JMS">         </jms:inbound-endpoint></jms:outbound-endpoint></request-reply>     </set-property></http:listener></flow>     <flow name="Process-Request-Order_Flow">         <jms:inbound-endpoint exchange-pattern="request-response" queue="order.request" connector-ref="Active_MQ" doc:name="JMS">         <set-payload value="This is a reply message with JMSCorrelationID=#[message.sku]!" doc:name="Set Payload">     </set-payload></jms:inbound-endpoint></flow> </mule>

This approach is clearly defined which queue the reply will be stored, instead of using unnamed temporary queue. In terms of clarity, this is better approach. However, in the clustering environment, this may be problematic. This needs to be confirmed with MuleSoft.