|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [jira] [Created] (CAMEL-5452) DoCatch doesn't notify... Raul Kripalani (JIRA)
- [jira] [Commented] (CAMEL-5452) DoCatch doesn't... Claus Ibsen (JIRA)
- [jira] [Updated] (CAMEL-5452) DoCatch doesn't n... Claus Ibsen (JIRA)
- [jira] [Comment Edited] (CAMEL-5452) DoCatch do... Raul Kripalani (JIRA)
- [jira] [Commented] (CAMEL-5452) DoCatch doesn't... Raul Kripalani (JIRA)
- [jira] [Commented] (CAMEL-5452) DoCatch doesn't... Claus Ibsen (JIRA)

I am not sure if this is really the intention of that even. The failure handled was intended for the error handler when it handles the exception.
I wonder if we want to emit the even as well for doTry .. doCatch, as that is no-surprise that this exception can occur?
We could of course introduce a flag on the event, to indicate it was from doTry / doCatch and emit it as well. Then ppl can filter it out if they want. Or we could introduce an new ExchangeDoCatchEvent
Any though?