> That only rough idea, but real solution should be more complicated. > It need to take in account the max number of attempts, > also the > otherwise().to("direct:beginPollQ") construction will send the "fail result" > to begin, not the token as expected.
I understand :) But I prefer to achieve my solution using "pure Camel" and switch to the custom glue code only when my Camel routes become too cluttered. In this case I'll still try to create Camel-based solution :) . Regarding the counter attempts - you still can hold this kind of information in the message header. -- Henryk Konsek http://henryk-konsek.blogspot.com