On Mon, Aug 20, 2012 at 9:29 AM, Neeraj Mahajan <neeraj.maha...@specsavers.com> wrote: > I have intentionally disabled the error handlling, As I *required the message > to be redelivered* in case of any exception/error in any route. I have > applied transaction policy in my root route(not shown here in the above code > sniphet) from where this splitter and aggregator gets called. >
The Aggregator EIP in Camel 1.x does *not* support redelivery or persistent storage out of the box. You would need Camel 2.3 onwards for that. If an exception occurs, you would have to deal with that and handle your own kind of redelivery. > Thanks > Neeraj Mahajan > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Aggregator-not-propagating-exception-back-in-camel-version-1-6-2-tp5717629p5717689.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
