Hi All,
I have a camel route, which takes messages from a jms queue and further
sends it down to a splitter. Further the responses are aggregated and sent
back to a response queue. (of course response queue is controller by the
client in this scenario )
In this scenario I had to manually handle client's correlation id, because
after aggregation the original correlation id will be obvious lost. Can we
add a jms option to handle this scenario ?
At the moment I am having this logic which manually reverts the original
correlation id.
<route id="test-gateway-jms-route">
<from
uri="jms:queue:Gateway-Queue?replyToDeliveryPersistent=false" />
<setProperty
propertyName="parkedClientCorrelationId"><simple>${headers.JMSCorrelationID}</simple></setProperty>
<removeHeader headerName="JMSCorrelationID" />
<to uri="direct:downstream-routes" />
<setHeader
headerName="JMSCorrelationID"><simple>${property.parkedClientCorrelationId}</simple></setHeader>
<removeProperty
propertyName="parkedClientCorrelationId" />
</route>
Cheers
Guru
@tallguru
--
View this message in context:
http://camel.465427.n5.nabble.com/Manage-CorrelationID-using-JMS-endpoint-options-tp5767995.html
Sent from the Camel - Users mailing list archive at Nabble.com.
