[
https://issues.apache.org/activemq/browse/SMXCOMP-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trevor Pounds updated SMXCOMP-568:
----------------------------------
Issue Type: Improvement (was: Bug)
> 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-2009.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.
-
You can reply to this email to add a comment to the issue online.
