anti-patterns.
Have you seen two way queue is shop? :)
Best regards,
Lukasz
-Original Message-
From: Willem Jiang [mailto:willem.ji...@gmail.com]
Sent: Thursday, January 20, 2011 8:31 AM
To: dev@camel.apache.org
Subject: Re: [DISCUSS] - JMSReplyTo to yourself
Yes, CXF JMS transport
...@gmail.com]
Sent: Thursday, January 20, 2011 8:31 AM
To: dev@camel.apache.org
Subject: Re: [DISCUSS] - JMSReplyTo to yourself
Yes, CXF JMS transport support to use same queue for request and
response, and it use the selector to check the correlationID.
I think the failed test is caused by the message
: [DISCUSS] - JMSReplyTo to yourself
Yes, CXF JMS transport support to use same queue for request and
response, and it use the selector to check the correlationID.
I think the failed test is caused by the message exchange pattern is
InOut, and if the test box is slower to shutdown the camel
I *think* I would leave it as is. You are right, This is a valid usecase *if*
selectors are used. The extra allowReplyToSameDestination configuration would
be required for this scenario. It gets trickier with dynamic recipients. This
makes configuration imho unnecessarily more complicated. This
Hi
Suppose you have a Camel route
from(activemq:queue:foo)
.process(xxx)
And a client sends a message to the foo queue with a JMSReplyTo header
set with the queue:foo destination.
The client has essentially told to send a reply back to the same queue
as the message was consumed.
Currently
Hi Claus,
most of the time, we have a REQUEST queue and a RESPONSE queue.
I've never seen a response post on the same queue.
By default, it makes sense to log a WARN when posting on the same queue.
The use of disableReplyTo is too restrictive because the users could use
a replyTo to another
Hi Claus,
I also have not seen people using the same queue for replies. Although
it would be possible o do so using message selectors. So if we want to
block this we should allow people to override. Something like
?allowReplyToSameDestination=true
Christian
Am 20.01.2011 07:38, schrieb
Yes, CXF JMS transport support to use same queue for request and
response, and it use the selector to check the correlationID.
I think the failed test is caused by the message exchange pattern is
InOut, and if the test box is slower to shutdown the camel context, you
will get as many as
