You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by Claus Ibsen <cl...@gmail.com> on 2014/07/05 10:43:57 UTC
Re: Enricher EIP skips AggregationStrategy if Exchange contains exception
Hi
A bit late for the reply. But I think you spotted something, so I
logged a ticket
https://issues.apache.org/jira/browse/CAMEL-7581
On Tue, Jan 28, 2014 at 12:34 PM, Elvio Caruana (ecaruana)
<ec...@cisco.com> wrote:
> Hi,
>
> Looking at the Enricher source code, it looks to me that if an exception is set and unhandled in a route called by the Enrich step, then the AggregationStrategy is skipped (although the state, including exceptions is copied over to the original exchange (Exchange. copyResultsPreservePattern(resultExchange, sourceExchange))
>
> But this means that this is different behaviour from the way exceptions have to be handled manually in the Splitter EIP. What's the reasoning behind this?
>
> Thanks,
> Elvio
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
RE: Enricher EIP skips AggregationStrategy if Exchange contains
exception
Posted by "Elvio Caruana (ecaruana)" <ec...@cisco.com>.
Thanks Claus.
Elvio
-----Original Message-----
From: Claus Ibsen [mailto:claus.ibsen@gmail.com]
Sent: 05 July 2014 09:44
To: users@camel.apache.org
Subject: Re: Enricher EIP skips AggregationStrategy if Exchange contains exception
Hi
A bit late for the reply. But I think you spotted something, so I logged a ticket
https://issues.apache.org/jira/browse/CAMEL-7581
On Tue, Jan 28, 2014 at 12:34 PM, Elvio Caruana (ecaruana) <ec...@cisco.com> wrote:
> Hi,
>
> Looking at the Enricher source code, it looks to me that if an
> exception is set and unhandled in a route called by the Enrich step,
> then the AggregationStrategy is skipped (although the state, including
> exceptions is copied over to the original exchange (Exchange.
> copyResultsPreservePattern(resultExchange, sourceExchange))
>
> But this means that this is different behaviour from the way exceptions have to be handled manually in the Splitter EIP. What's the reasoning behind this?
>
> Thanks,
> Elvio
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/