Mailing-List: contact dev-help@servicemix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@servicemix.apache.org
Date: Sun, 6 Feb 2011 09:51:33 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: dev@servicemix.apache.org
Message-ID: 
 <1821341250.2539.1296985893057.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (SMXCOMP-568) EIP Filter should propagate
 exceptions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/SMXCOMP-568?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofr=C3=A9 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-r78424=
8.diff
>
>
> Currently the EIP Filter component does not send back exceptions (i.e. or=
g.xml.sax.SAXParseException) as an error on the exchange which is the defau=
lt behavior for other components (i.e. servicemix-saxon).  As a result, the=
re 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() me=
thod to handle the exception and send it as an error on the exchange.

--=20
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira