This one just won't die :) I've got the same issue, but caused in a slightly different way. The problem is when the DB commit fails (in my case, a unique constraint violation to an Oracle DB), the commit happens outside of the TransactionErrorHandler.super.process(exchange) block, and won't trigger the global onException handlers.
I've tried to create a unit test to show the issue, but I cannot figure out how to make HSQL throw an exception at commit time. If anyone has any tips I'd be happy to create a unit test. Thanks, Dan Nawrocki Claus Ibsen-2 wrote: > > On Fri, Apr 9, 2010 at 8:46 PM, dnn <daniel.nawro...@ngc.com> wrote: >> >> Works for me too using trunk. It looks like an automated build pulls the >> trunk at midnight and deploys it to 2.3-SNAPSHOT in maven, so I should be >> able to start using it from mvn tomorrow. When is 2.3.0 slated for >> release? >> > > There are still a couple of must work to be done. (restore camel-http > using http client 3.1 as http client 4.0.1 lacks some features in 3.1, > and those features have only been added to http client 4.1, which goes > on a long release path with alpha releases currently :( :( > > I think we can have it released in end of this or start of next month. > -- View this message in context: http://old.nabble.com/onException-handling-tp28183226p28245275.html Sent from the Camel - Users mailing list archive at Nabble.com.
