Return-Path: 
 <users-return-31809-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
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 63043DBEA
	for <apmail-camel-users-archive@www.apache.org>;
 Fri, 17 Aug 2012 17:01:39 +0000 (UTC)
Received: (qmail 22586 invoked by uid 500); 17 Aug 2012 17:01:39 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 22552 invoked by uid 500); 17 Aug 2012 17:01:38 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 22541 invoked by uid 99); 17 Aug 2012 17:01:38 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Aug 2012 17:01:38 +0000
X-ASF-Spam-Status: No, hits=0.6 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.217.173 as permitted sender)
Received: from [209.85.217.173] (HELO mail-lb0-f173.google.com)
 (209.85.217.173)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Aug 2012 17:01:33 +0000
Received: by lbbgm13 with SMTP id gm13so2485018lbb.32
        for <users@camel.apache.org>; Fri, 17 Aug 2012 10:01:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=nIe3C68PWjmFB5skFmEkCiFzABGLeJImMZ8LdNm3dhY=;
        b=SQhcnmXcdE3kpdk4BRjatzUodSZdo5dAMqG+wap6hbmMg9eJ0JlVpoEz0l+oA8Nr18
         gKHcVSl8KYbpnlygZF9IR95sR4G3wCYBVDTgcZr+z1TaW5iWWS3EL5tmVvRt/PFSfdf8
         AXlWyLE1mfWCIJiZIeXdpZWrM4U0meAjRi3ny6Y2VuPXpltrRKAjbU9G8eZ84yWE7FXv
         2qZ+R82tZk6UlWrVqT2sk7cjJGBAOqpqAtkaY8IIXv0R3VHFeTufNbFC7DCXA/eBhOst
         co3tT8hqvqDoJmFDsvkt9jaBHZfBhnDuxcowK1NGypFDHBNMPQIefvlwnaAGLKHC7Ykd
         Jj7g==
Received: by 10.152.111.71 with SMTP id ig7mr2475492lab.28.1345222872820; Fri,
 17 Aug 2012 10:01:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.112.7.230 with HTTP; Fri, 17 Aug 2012 10:00:52 -0700 (PDT)
In-Reply-To: <1345219544030-5717629.post@n5.nabble.com>
References: <1345219544030-5717629.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Fri, 17 Aug 2012 19:00:52 +0200
Message-ID: 
 <CAGB5yNnmigyTQBKjd6FPpGUYEw_7o0sULDJASjho=7yyh4-4YQ@mail.gmail.com>
Subject: Re: Aggregator not propagating exception back in camel version 1.6.2
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Camel 1.x is EOL and no longer supported at Apache.

in your custom aggregatorStrategy you should be able to get the caused
exception on the exchange. And decide what to do.

On Fri, Aug 17, 2012 at 6:05 PM, Neeraj Mahajan
<neeraj.mahajan@specsavers.com> wrote:
> I am calling a route from Aggregator using direct component once  aggregation
> is complete.
> When the called direct route throws any Exception I expect that aggregator
> *should not handle* that exception, but the problem I am facing is that the
> exception is being getting handled by the aggregator which i dont require.
>
> I am using camel *1.6.2 version* and i can't ugrade to newer versions.
> Following is code snippet i am using
>
> <route id="splitterRoute" errorHandlerRef="noErrorHandlerBuilder">
> <splitter>
>                 <xpath>/ord:orderSet/ord:orders/ord:order</xpath>
>                 <process ref="myProcessor" />
>                 <to uri="direct:aggregatorRoute" />
> </splitter>
> </route>
>
> <route id="aggregatorRoute" errorHandlerRef="noErrorHandlerBuilder">
>                         <from uri="direct:aggregatorRoute" />
>                         <aggregator strategyRef="aggregatorStrategy" >
>                                 <simple>header.JMSCorrelationID</simple>
>                                 <to uri="direct:responseGenerationRoute"/>
>                                 <completedPredicate>
>                                         <methodCall bean="aggregationCompletionStrategy"
> method="aggregationComplete" />
>                                 </completedPredicate>
>                         </aggregator>
> </route>
>
> <route id="responseGenerationRoute" errorHandlerRef="noErrorHandlerBuilder">
>                 <from uri="direct:responseGenerationRoute" />
>                 <process ref="responseGenerationProcessor" />
>                         <recipientList>
>                                 <header>responseDestination</header>
>                         </recipientList>
> </route>
>
> It will be helpfull, If someone can provide any direction on this.
>
> Thanks in Advance
> Neeraj
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Aggregator-not-propagating-exception-back-in-camel-version-1-6-2-tp5717629.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen