want to dispatch your reply messages to different
> endpoints without selectory?
>
> -Original Message-
> From: James Carman [mailto:ja...@carmanconsulting.com]
> Sent: Mittwoch, 13. Juli 2016 13:11
> To: dev@camel.apache.org
> Subject: Re: [DISCUSS] Reusing Exclusive ReplyTo
mes Carman [mailto:ja...@carmanconsulting.com]
Sent: Mittwoch, 13. Juli 2016 13:11
To: dev@camel.apache.org
Subject: Re: [DISCUSS] Reusing Exclusive ReplyTo Queue..
Shared uses selectors. There's no reason to use selectors in my case
On Wed, Jul 13, 2016 at 6:31 AM Siano, Stephan
wrote:
&
gt; wrong here?
>
> -Original Message-
> From: James Carman [mailto:ja...@carmanconsulting.com]
> Sent: Dienstag, 12. Juli 2016 15:47
> To: dev@camel.apache.org
> Subject: Re: [DISCUSS] Reusing Exclusive ReplyTo Queue..
>
> I am not talking about using a Shared reply queue. I'm
Subject: Re: [DISCUSS] Reusing Exclusive ReplyTo Queue..
I am not talking about using a Shared reply queue. I'm talking about using
Exclusive. The idea would be to be able to send messages, using a
ProducerTemplate or something, like this:
jms:queue:foo?replyToType=Exclusive&replyT
I am not talking about using a Shared reply queue. I'm talking about using
Exclusive. The idea would be to be able to send messages, using a
ProducerTemplate or something, like this:
jms:queue:foo?replyToType=Exclusive&replyTo=REPLIES&concurrentConsumers=5
jms:queue:bar?replyToType=Exclusive&rep
Hi James,
I am not sure whether I understand the context. Are you talking about
request/reply over JMS with the camel-jms component?
In that case the replyToDestinationSelectorName parameter might help you with
shared reply to queues. I actually do not see any impact that may have on
transacti
