servicemix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré (JIRA) <j...@apache.org>
Subject [jira] Updated: (SMXCOMP-568) EIP Filter should propagate exceptions
Date Sun, 06 Feb 2011 09:51:33 GMT

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

Jean-Baptiste Onofré updated SMXCOMP-568:
-----------------------------------------

    Fix Version/s:     (was: 2011.01)
                   2011.02

> EIP Filter should propagate exceptions
> --------------------------------------
>
>                 Key: SMXCOMP-568
>                 URL: https://issues.apache.org/jira/browse/SMXCOMP-568
>             Project: ServiceMix Components
>          Issue Type: Improvement
>          Components: servicemix-eip
>    Affects Versions: servicemix-eip-2009.01
>            Reporter: Trevor Pounds
>             Fix For: 2011.02
>
>         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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message