I'm trying to figure out how to set up a route that will put a message to an
activemq queue and will continue processing the rest of route without
waiting for the route listening on the activemq queue to complete. I
thought I could accomplish this by doing something like this.
from("seda:blah").
process(new ProcessorA()).
to("activemq:queueA"). // another route is set to pick this up
process(new ProcessorB());
When I run a message through I don't get to ProcessorB until the route
listening on queueA completes. I was thinking that the
to("activemq:queueA") would do a simple put to the queue and then
immediately continue on with processing the rest of the route. Any thoughts
on what I'm missing here?
--
View this message in context:
http://www.nabble.com/Put-to-queue-and-continue-processing-tp16850731s22882p16850731.html
Sent from the Camel - Users mailing list archive at Nabble.com.
