...
In Camel we prefix the keywords with do
to avoid having same keyword as Java. So we have:
doTry
doCatch
doFinally
end
to end the block in Java DSL
Notice this document is based on how it works in Camel 2.0. In Camel 1.x this feature isn't as powerful and it uses a slight different keyword names.
...
When using doTry .. doCatch .. doFinally
then the regular Camel Error Handler does not apply. That means any onException
or the likes does not trigger. The reason is that doTry .. doCatch .. doFinally
is in fact its own error handler and that it aims to mimic and work like how try/catch/finally works in Java.
...
In the route below we have all keywords in action. As the code is based on a unit test we route using Mock.
...
And in the route below we want to indicate if an IOException occured we want to route it elsewhere and at the same time keep the exception so the original caller is notified about this exception. To do this we need to not rethrow the exception and this is why we use handled and set it to false to indicate, no we did not handle it so please keep the exception.
The 2nd exception block can be omitted but as the code is based on an unit test we want to test the behavior non IOException
as well.
...
...
And finally we have an example of the onWhen
predicate in action. We can attach it to a doCatch
block and at runtime determine if the block should be triggered or not.
In our case we only want to trigger if the caused exception message contains the damn word.
...
Notice when using Java DSL we must use end()
to indicate where the try .. catch .. finally block ends. As the example above has a finally, then the end()
should be at the end of the finally block. If we are not using a finally, then the end()
should be at the end of the doCatch
to indicate the end there.
...
In the route below we have all keywords in action. As the code is based on a unit test we route using Mock.
...
...
And in the route below we want to indicate if an IOException occured we want to route it elsewhere and at the same time keep the exception so the original caller is notified about this exception. To do this we need to not rethrow the exception and this is why we use handled and set it to false to indicate, no we did not handle it so please keep the exception.
The 2nd exception block can be omitted but as the code is based on an unit test we want to test the behavior non IOException
as well.
...
And finally we have an example of the onWhen
predicate in action. We can attach it to a doCatch
block and at runtime determine if the block should be triggered or not.
In our case we only want to trigger if the caused exception message contains the damn word.
...
...