I tried adding disableReplyTo=true on the queue, but it still ended up with
an InOut exchange pattern so the JmsProducer code was still waiting for the
response. I looked around for a way to set the exchange pattern explicitly,
but by your response it sounds like there isn't currently a way to do that.
I ended up creating a processor that did the put to the queue without
waiting for a response similar to how the else branch in JmsProducer does it
and that got me the behavior I was looking for. Thanks for helping to point
me toward a solution.
As an aside, Camel is just plain outstanding. What a great lightweight and
powerful framework you guys have put together.
James.Strachan wrote:
>
> Does the message you are sending to queueA have a JMSReplyTo header?
> If so camel by default assumes its an InOut pattern (i.e.
> request/response).
>
> You can configure the endpoint to ignore the JMSReplyTo...
>
> to("activemq:queueA?disableReplyTo=true")...
>
>
> One thing we should maybe do is add an explicit exchange pattern verbs
> to the DSL. So you could be more explicit....
>
> from(a).request(b).oneway(c)
>
> i.e. to be explicit about whether or not you want a one way (InOnly)
> or request/response (InOut) rather than reply on the component to
> deduce the right thing
>
--
View this message in context:
http://www.nabble.com/Put-to-queue-and-continue-processing-tp16850731s22882p16917646.html
Sent from the Camel - Users mailing list archive at Nabble.com.
