camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Bischoff <jbisch...@wdtablesystems.com>
Subject Re: Using non-standard JMS correlation ID
Date Thu, 10 Jul 2014 14:26:49 GMT
Hmm I meant to link you to the *exclusive* fixed reply queue, not the
shared one.

Correct link:
http://camel.apache.org/jms.html#JMS-Request-replyoverJMSandusinganexclusiv
efixedreplyqueue


Jeff

On 7/10/14 10:24 AM, "Jeff Bischoff" <jbischoff@wdtablesystems.com> wrote:

>Hi Kev,
>
>I believe you can use an exclusive fixed reply queue for that.
>
>Please see:
>http://camel.apache.org/jms.html#JMS-AboutusingCameltosendandreceivemessag
>e
>sandJMSReplyTo
>And especially see:
>http://camel.apache.org/jms.html#JMS-Request-replyoverJMSandusingasharedfi
>x
>edreplyqueue
>
>I've had some trouble with this problem myself. Hopefully it helps you!
>
>Jeff
>
>On 7/10/14 5:51 AM, "kev" <kboone@redhat.com> wrote:
>
>>Hi all
>>
>>I'm trying to create a Camel route that will post a message to a legacy
>>system with a JMS interface, and wait for a reply on a specific JMS
>>queue.
>>This seems to be a pretty standard use of the inout exchange pattern.
>>However, the legacy system does not use the standard JSMCorrelationID
>>header
>>to associate outbound messages with their inbound requests. Instead, it
>>uses
>>an entirely non-standard header.
>>
>>As I understand it, if I use
>>
>>from (jms:something).inout(jms:something?replyTo=output_queue)
>>
>>then Camel will use JMSCorrelationID to match the inbound and outbound
>>messages. However, is there any way that inout() can be configured to use
>>some other header?
>>
>>If not, is there some other way to approach this problem using standard
>>Camel features?
>>
>>Thanks
>>Kev
>>
>>
>>
>>
>>--
>>View this message in context:
>>http://camel.465427.n5.nabble.com/Using-non-standard-JMS-correlation-ID-t
>>p
>>5753642.html
>>Sent from the Camel - Users mailing list archive at Nabble.com.
>
>________________________________
>
>Please take note: This email, including attachments, contains information
>which may be confidential or legally privileged and is only for the use
>of the individual or entity to whom it is properly addressed. Any
>unauthorized review, use, disclosure, copying, or distribution is
>prohibited. If you have reason to believe that you have received this
>communication in error, or that it may be misaddressed or not intended
>for you, please destroy it and notify the sender immediately. Thank you.

________________________________

Please take note: This email, including attachments, contains information which may be confidential
or legally privileged and is only for the use of the individual or entity to whom it is properly
addressed. Any unauthorized review, use, disclosure, copying, or distribution is prohibited.
If you have reason to believe that you have received this communication in error, or that
it may be misaddressed or not intended for you, please destroy it and notify the sender immediately.
Thank you.

Mime
View raw message