On 2012-02-03 4:58 PM, Babak Vahdat wrote:
Instead of using a ProducerTemplate it would be much easier to do a to("...")
to fire an exchange into your second route inside the same camel context.
Those were my exact words to my colleague:) He told me that the
separate ProducerTemplate was used to do a synchronous type operation.
I'm going to play around with that for a bit and see if I can collapse
it all into one Camel route, as you suggest.
And if you want to access the Exception attached to the failed exchange you
can make use of a Processor or your Bean (Bean-Binding) inside your
onException clause where using exchange.getException() would deliver you the
attached exception by the given exchange.
That is what I was expecting. I see your next response. I'll check
that property.
Thanks.
