[
https://issues.apache.org/activemq/browse/CAMEL-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1560.
--------------------------------
Resolution: Fixed
trunk: 768215
The bullet #1 is the most correct to use as it mimics how the Java try .. catch
will behave.
And I was wrong before #1 has been the default in Camel 1.x all the way.
> try ... catch .. finally and error handler
> ------------------------------------------
>
> Key: CAMEL-1560
> URL: https://issues.apache.org/activemq/browse/CAMEL-1560
> Project: Apache Camel
> Issue Type: Task
> Components: camel-core
> Affects Versions: 2.0-M1
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.0.0
>
>
> What should be the strategy for error handler in the route with the try ..
> catch .. finally blocks?
> 1)
> Error handler is disabled
> 2)
> Error handler is enabled, and doTry gets what its left. e.g. error Handler
> take precedence over doTry
> 3)
> Error handler is enabled but doCatch take precedence over the existing
> onException defined at the error handler (if any)
> 4)
> doCatch to support redelivery as well? Kinda hard ball.
> The possibilities are many but we need to settle on a strategy that has no
> surprises for the end users.
> PS: The current strategy in the code is #2.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
