On Wed, Jul 11, 2012 at 5:22 PM, Hilde <[email protected]> wrote: > Hello fellows! > > Can somebody explain me why the exception handling in camel can be > non-handeld? Furthermore that is the default if you are using >
People have different use-case how to deal with that, and thus they have a choice. > /*onExchange(Exception.class).end()*/ > Yes this does not make sense to do. In Camel 3.0 we will improve the DSL to be more strict and invalidate such kind of configurations. > In my opinion it makes no sense when you cannot handle the exception. And > what impacts has the > construct above in a route scope anyway? It is not revealed to me what makes > the difference in omit or apply it - the exception is thrown anyway. > Error handling is hard, so take your time to read the docs, and other links / blog posts etc. http://camel.apache.org/error-handling-in-camel.html http://www.consulting-notes.com/2010/08/camel-exception-handling-overview.html And if you have a copy of Camel in Action, then chapter 5 is entirely devoted to error handling. > Cheers > Hilde > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Basic-knowledge-onException-tp5715861.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
