Hi I WAS WRONG with my bug assumption, see the answer here:
http://camel.465427.n5.nabble.com/Is-this-routing-behaviour-as-expected-td5717331.html Sorry for the noise & confusion. Babak Aleksander Pena wrote > > 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(TIMEOUT)) > .otherwise() > .enrich("direct:emulateNonLegacyHttp").timeout(property(TIMEOUT)) > .end() > > Unfortunately I cannot find timeout with argument of Expression type :( > > It would be the best if I could specify timeout per each flow in route > like > in the below excerpt: > > from("direct:start") > .timeout(property(TIMEOUT)) > .process(new SomeProcessingHere()) > .to("direct:anotherEndpoint"); > > But probably it is difficult to implement such behaviour in Camel. > > Anyway there is still open question why my original example doesn't work. > Is it really a bug in Camel as Babak suggesting? > > Thanks for help, > Alek > -- View this message in context: http://camel.465427.n5.nabble.com/Splitter-aggregator-dynamic-timeout-tp5717166p5717357.html Sent from the Camel - Users mailing list archive at Nabble.com.
