ah, sorry, forgot that there is a JMSRouter - solved the problem with it :)
Would you please share more info on your solution? Thanks
I only added a action with JMSRouter to the action pipeline, which sends the answer from the previous actions to a given JMS-queue:
<actions mep="OneWay"> <action name="anyActions" class="org.jboss.soa.esb.actions.soap.SOAPClient"> <property name="wsdl" value="http://somewhere/svc?wsdl" /> <property name="SOAPAction" value="doSomething" /> </action> <!-- some more actions if required --> <action name="routeBack" class="org.jboss.soa.esb.actions.routing.JMSRouter"> <property name="jndiName" value="queue/inet_esb_test_echojms_soapclient_reply" /> <property name="unwrap" value="true" /> </action> </actions>
Another possibility (without JMSRouter) is to set JMSReplyTo before sending the message to the bus:
ObjectMessage msg = session.createObjectMessage(content); msg.setJMSReplyTo(jmsReplyDestination); ...
The Property MEP has to be set to "RequestResponse" in this case. Additionally, the message you get back isn't unwrapped, thus not really understandable for a ESB-unaware receiver. So I prefer the first solution.
Hope this helps