You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2009/12/23 06:11:43 UTC

[jira] Updated: (SMXCOMP-568) EIP Filter should propagate exceptions

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

Gert Vanthienen updated SMXCOMP-568:
------------------------------------

    Fix Version/s:     (was: servicemix-eip-2009.02)
                   servicemix-eip-2010.01

> EIP Filter should propagate exceptions
> --------------------------------------
>
>                 Key: SMXCOMP-568
>                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-568
>             Project: ServiceMix Components
>          Issue Type: Improvement
>          Components: servicemix-eip
>    Affects Versions: servicemix-eip-2009.01
>            Reporter: Trevor Pounds
>             Fix For: servicemix-eip-2010.01
>
>         Attachments: SMXCOMP-568-3.3.18-fuse.diff, SMXCOMP-568-SVN-r784248.diff
>
>
> Currently the EIP Filter component does not send back exceptions (i.e. org.xml.sax.SAXParseException) as an error on the exchange which is the default behavior for other components (i.e. servicemix-saxon).  As a result, there is no way to capture the message that generated the exception. We should change the implementation to propagate the exception up the call stack to allow the org.apache.servicemix.common.BaseLifeCycle.onMessageExchange() method to handle the exception and send it as an error on the exchange.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.