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 D66B684A1 for ; Thu, 1 Sep 2011 16:31:43 +0000 (UTC) Received: (qmail 93100 invoked by uid 500); 1 Sep 2011 16:31:43 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 92887 invoked by uid 500); 1 Sep 2011 16:31:42 -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 92879 invoked by uid 99); 1 Sep 2011 16:31:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2011 16:31:42 +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 (athena.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; Thu, 01 Sep 2011 16:31:36 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QzAAd-0002Kx-10 for users@camel.apache.org; Thu, 01 Sep 2011 09:31:15 -0700 Date: Thu, 1 Sep 2011 09:31:15 -0700 (PDT) From: Jens To: users@camel.apache.org Message-ID: <1314894675024-4759049.post@n5.nabble.com> In-Reply-To: <1314627151282-4746297.post@n5.nabble.com> References: <1305121632476-4387421.post@n5.nabble.com> <1305127066522-4387637.post@n5.nabble.com> <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> Subject: Re: Does onException not support multiple statements? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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 exchange.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. Jens -- View this message in context: http://camel.465427.n5.nabble.com/Does-onException-not-support-multiple-statements-tp4381958p4759049.html Sent from the Camel - Users mailing list archive at Nabble.com.