Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 12 Jul 2015 11:56:05 +0000 (UTC)
From: "Andy Fedotov (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: <JIRA.12844425.1436702131000.164467.1436702165055@Atlassian.JIRA>
In-Reply-To: <JIRA.12844425.1436702131000@Atlassian.JIRA>
References: <JIRA.12844425.1436702131000@Atlassian.JIRA>
 <JIRA.12844425.1436702131491@arcas>
Subject: [jira] [Created] (CAMEL-8955) Processor for .pollEnrich incorrectly
 handles provided AggregationStrategy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Andy Fedotov created CAMEL-8955:
-----------------------------------

             Summary: Processor for .pollEnrich incorrectly handles provided AggregationStrategy
                 Key: CAMEL-8955
                 URL: https://issues.apache.org/jira/browse/CAMEL-8955
             Project: Camel
          Issue Type: Bug
          Components: camel-core
    Affects Versions: 2.14.3
            Reporter: Andy Fedotov
            Priority: Minor


As it can be concluded from AggregationStrategy javadoc, and also from available implementations such as GroupedExchangeAggregationStrategy, it should be used in the following manner:

{code:java}
AggregationStrategy strategy = new GroupedExchangeAggregationStrategy();

Exchange result = null;
result = strategy.aggregate(result, exchange1);
result = strategy.aggregate(result, exchange2);
// ... and so on
return result;
{code}

But PollEnricher do it in following manner:

{code:java}
AggregationStrategy strategy = new GroupedExchangeAggregationStrategy();

Exchange result = strategy.aggregate(exchange1, exchange2);
return result;
{code}

This leads to incorrect result returned after aggregation and lost exchanges.

Also PollEnricher doesn't handle CompletionAwareAggregationStrategy and does not call onCompletion(). Consequently GroupedExchangeAggregationStrategy does not return aggregated result in the Exchange body.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)