Re: question about exception handling behavior

2013-11-19 Thread Michiel Borkent
Dear Christian, This seems to work. Thank you! Michiel -- View this message in context: http://camel.465427.n5.nabble.com/question-about-exception-handling-behavior-tp5743489p5743537.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: question about exception handling behavior

2013-11-19 Thread Christian Posta
I've updated my response in your gist. In short, Apache Camel will create a separate Channel construct under the covers for your advice-with route builder. This means the advice builder won't see the try-catch at that point since the try-catch is in a separate route. To test what you're trying to

Re: question about exception handling behavior

2013-11-19 Thread Christian Posta
Use skipSendToOriginalEndpoint(). I left a comment on your gist. Alternatively, since you're just using a mock endpoint, you can just use the mock to throw the exception: getMockEndpoint("mock:exception").whenAnyExchangeReceived(new Processor() { @Override public

Re: question about exception handling behavior

2013-11-19 Thread Michiel Borkent
I mean the onException block Michiel Borkent Software Engineer Finalist - open *IT* oplossingen Amsterdam - Eindhoven - Maarssen - Maastricht - Rotterdam *www.finalist.nl * 2013/11/19 Michiel Borkent > Hi, > > In the following code: https://gist.github.com/anonymous/