Splitter + aggregator + dynamic timeout

2012-08-12 Thread Aleksander Pena
Hi guys, I have specific requirements. Incoming request should be split into same another requests and sent to different sources paralelly. The sources (legacy and new) are almost compatible with each other but legacy responds much slower than new. To prevent degradation of the whole service inco

Re: Splitter + aggregator + dynamic timeout

2012-08-12 Thread Aleksander Pena
Hi Henryk, > First of all - apparently you forgot to add the routes examples to the > message. :) Could you send them here? I'm not sure if the example I've added in the original message is visible by you? I've added example route to the message above and it is visible via web page.Please advice

Re: Splitter + aggregator + dynamic timeout

2012-08-13 Thread Aleksander Pena
Henryk, thanks for another way of resolving my requirements it works perfectly well, but there are missing some important req: I need to setup timeout dynamically, so the flow could looks like following: .when(body().isEqualTo("foo")) .enrich("direct:emulateLegacyHttp").timeout(property(TIME

Re: Splitter + aggregator + dynamic timeout

2012-08-16 Thread Aleksander Pena
Hi Babak, your solution works fine but you removed parallel processing which is important for me :) Anyway I found solution for my original problem: 1. before processing is started I'm storing current exchange (from a main thread) as a property (myEx). Then myEx property is propagated to splitter