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
't tried that out myself, though.
>
> Best regards
> Stephan
>
> -Original Message-
> From: James Carman [mailto:ja...@carmanconsulting.com]
> Sent: Montag, 11. Juli 2016 16:29
> To: dev@camel.apache.org
> Subject: [DISCUSS] Reusing Exclusive ReplyTo Queue..
>
transactions. I haven't tried that out myself, though.
Best regards
Stephan
-Original Message-
From: James Carman [mailto:ja...@carmanconsulting.com]
Sent: Montag, 11. Juli 2016 16:29
To: dev@camel.apache.org
Subject: [DISCUSS] Reusing Exclusive ReplyTo Queue..
Right now, you must have a u
Right now, you must have a unique reply to queue for each destination.
Would there be any impact of allowing folks to use a single reply to queue
for all destinations? For example, suppose I want to use an "Exclusive"
reply to queue per node within my cluster, but I want all replies (for all
route
