Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 83F9A7973 for ; Fri, 2 Sep 2011 12:23:51 +0000 (UTC) Received: (qmail 62169 invoked by uid 500); 2 Sep 2011 12:23:51 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 61983 invoked by uid 500); 2 Sep 2011 12:23:48 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 61974 invoked by uid 99); 2 Sep 2011 12:23:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Sep 2011 12:23:47 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Sep 2011 12:23:41 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QzSmG-0003Q6-2v for users@camel.apache.org; Fri, 02 Sep 2011 05:23:20 -0700 Date: Fri, 2 Sep 2011 05:23:20 -0700 (PDT) From: Jens To: users@camel.apache.org Message-ID: <1314966200084-4762156.post@n5.nabble.com> In-Reply-To: References: <1305133015093-4387905.post@n5.nabble.com> <1305189978389-4389656.post@n5.nabble.com> <1305207076029-4390239.post@n5.nabble.com> <1305215368410-4390611.post@n5.nabble.com> <1305218245338-4390795.post@n5.nabble.com> <1314627151282-4746297.post@n5.nabble.com> <1314894675024-4759049.post@n5.nabble.com> Subject: Re: Does onException not support multiple statements? MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Claus Ibsen-2 wrote: >=20 > On Thu, Sep 1, 2011 at 6:31 PM, Jens wrote: >> koseki nonuyuki wrote: >>> I encountered the same trouble when I got SOAP fault. >>> >>> The first processor in the onException route, I put >>> "exchange.getOut().setBody(null)" , then multiple >>> process worked. >>> >>> When onException route received SOAP fault, the outMessage already >>> contains Exception info, that >>> cause another Exception at the next process and rollback, I guess. >> >> I'm doing the same thing, plus >> >> =C2=A0 =C2=A0 =C2=A0exchange.setProperty(Exchange.EXCEPTION_CAUGHT, >> exchange.getOut.getBody()); >> >> before that so the exception remains accessible. It seems to me that's >> what >> the onException handler should do already, though. >> >=20 > SOAP Faults is not part of the Camel error handling by default. >=20 > There is a handle fault (interceptor) you can enable which turns a > SOAP Fault -> Exception, > which the Camel error handler will be abel to detect and react upon. >=20 Hi Claus, as I wrote previously, handleFault doesn't seem to work in this case (Camel 2.6.0). Regards, Jens -- View this message in context: http://camel.465427.n5.nabble.com/Does-onExce= ption-not-support-multiple-statements-tp4381958p4762156.html Sent from the Camel - Users mailing list archive at Nabble.com.