You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Nilesh Soni (Updated) (JIRA)" <ji...@apache.org> on 2011/11/27 15:24:40 UTC

[jira] [Updated] (CAMEL-4482) Using custom expression in Splitter EIP which throws exception, is not triggering onException

     [ https://issues.apache.org/jira/browse/CAMEL-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nilesh Soni updated CAMEL-4482:
-------------------------------

    Comment: was deleted

(was: Hi Clause,
It seems that this issue is not yet resolved. Can you please try the code uploaded by me in the nabble http://camel.465427.n5.nabble.com/Global-exception-not-invoked-in-case-of-Exception-fired-while-iterating-through-File-Splitter-td4826097.html See the file SplitInProgress.java 

You just have to make sure following the create the failed scenario:
1) Commenting the exception with message "Let me throw my exception here to simulate XSD..."
2) Uncomment the line which throws the exception with message "Some business validation failed." 

And the exception will not be caught by the clause
onException(Throwable.class)
                        .process(customMoveFailed());)
    
> Using custom expression in Splitter EIP which throws exception, is not triggering onException
> ---------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-4482
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4482
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.8.2, 2.9.0
>
>
> See nabble
> http://camel.465427.n5.nabble.com/Global-exception-not-invoked-in-case-of-Exception-fired-while-iterating-through-File-Splitter-td4826097.html
> We should detect exceptions occurred during evaluation of the expression, and then cause the splitter EIP to fail asap.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira