Hi Jens,
why do you set replyDestination and replyToDestination to different
names? I don´t think that this can work.
The JMSConduit will always specify the replyDestination in the message
it sends out. So the server should always send the reply there.
When receiving the JMSConduit will use the replyToDestination if it is
set. So it will probably never receive anything.
Christian
Am 30.09.2011 15:50, schrieb Jens:
Hi Christian,
that won't work, primarily because I'm not allowed to use temporary queues
(company policy) and the server is listening on a remote queue manager, so
if I leave out replyToDestination it won't know where to send the reply.
Jens
Christian Schneider wrote:
Hi Jens,
why don´t you simply leave out replyDestination, replyToDestination,
useConduitIdSelector, conduitIdSelectPrefix.
Then cxf will use a temp queue for replies and the correlation should
still work. Can you try this with the newest CXF?
Christian
Am 30.09.2011 15:25, schrieb Jens:
This is what worked with 2.2 (angle brackets replaced to get through
Nabble):
[bean id="jmsConfig"
class="org.apache.cxf.transport.jms.JMSConfiguration"]
[property name="connectionFactory" ref="jmsConnectionFactory"/]
[property name="targetDestination"
value="queue:///out.queue?targetClient=1"/]
[property name="replyDestination" value="queue:///in.queue"/]
[property name="replyToDestination" value="queue://oqm/in.queue"/]
[property name="receiveTimeout" value="30000"/]
[property name="useConduitIdSelector" value="true"/]
[property name="conduitSelectorPrefix" value="ID:"/]
[property name="messageType" value="byte"/]
[property name="useMessageIDAsCorrelationID" value="true"/]
[/bean]
Jens
--
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
