Re: Asynchronous processing of routes

2014-01-07 Thread Henryk Konsek
Correct me if I am wrong. Camel will correlate the response if the other service sends back the response with the same correlation ID as was sent to it in the Request. In our case, the other services are third-party C++ services which work directly with MQ and do not use Camel. Reply

Re: Asynchronous processing of routes

2014-01-05 Thread Claus Ibsen
far indicate that I should keep consuming from MQ2 till I get M2 and then proceed with Route1. This means the RouteX and RouteY will never get the messages as they have been consumed by Route1. -- View this message in context: http://camel.465427.n5.nabble.com/Asynchronous-processing

Re: Asynchronous processing of routes

2014-01-05 Thread kraythe .
consuming from MQ2 till I get M2 and then proceed with Route1. This means the RouteX and RouteY will never get the messages as they have been consumed by Route1. -- View this message in context: http://camel.465427.n5.nabble.com/Asynchronous-processing-of-routes-tp5745385p5745542.html

Re: Asynchronous processing of routes

2014-01-05 Thread yashgt
fills the right correlation ID. But in my case the responder does not fill the correlation ID. Thanks, Yash -- View this message in context: http://camel.465427.n5.nabble.com/Asynchronous-processing-of-routes-tp5745385p5745569.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Asynchronous processing of routes

2014-01-05 Thread yashgt
to find the correlation ID in the Request and where to put it in the Response. In our case, the other services are third-party C++ services which work directly with MQ and do not use Camel. -- View this message in context: http://camel.465427.n5.nabble.com/Asynchronous-processing-of-routes

Re: Asynchronous processing of routes

2014-01-04 Thread yashgt
-processing-of-routes-tp5745385p5745542.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Asynchronous processing of routes

2014-01-03 Thread Henryk Konsek
Hi Yash, Solution to your problem is probably easier than you think. Using aggregator [1] EIP should solve your issue. from(jms:Q1).bean(SomeProcessorBean.class).to(jms:Q2); from(Q2). aggregate().constant(true).completionPredicate(body().isEqualTo(M2)).groupExchanges(). to(Q3); Aggregation

Re: Asynchronous processing of routes

2014-01-02 Thread Richard Kettelerij
-processing-of-routes-tp5745385.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Asynchronous processing of routes

2014-01-02 Thread kraythe .
for sure that among all the parallely executing routes, only one may wait for M2. What do we need to do to resume the route? Thanks, Yash -- View this message in context: http://camel.465427.n5.nabble.com/Asynchronous-processing-of-routes-tp5745385.html Sent from the Camel - Users

Asynchronous processing of routes

2014-01-01 Thread yashgt
.465427.n5.nabble.com/Asynchronous-processing-of-routes-tp5745385.html Sent from the Camel - Users mailing list archive at Nabble.com.