camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Carter (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CAMEL-7838) Aggregator - Using groupExchanges should store them on body mid-processing
Date Fri, 19 Sep 2014 09:26:33 GMT
Marc Carter created CAMEL-7838:
----------------------------------

             Summary: Aggregator - Using groupExchanges should store them on body mid-processing
                 Key: CAMEL-7838
                 URL: https://issues.apache.org/jira/browse/CAMEL-7838
             Project: Camel
          Issue Type: Improvement
          Components: camel-core
    Affects Versions: 2.13.2
            Reporter: Marc Carter
            Priority: Minor


CAMEL-6744 encompassed setting the List<V> into the body {{onCompletion}} only when
using anything based on {{AbstractListAggregationStrategy}}

However any strategies based on this class cannot be used with a persistent repository because
the GROUPED_EXCHANGE property appears not to be serialised so keeps being reset to the latest
message only.
(I spotted this by checking properties in the completion predicate and AGGREGATED_SIZE !=
GROUPED_EXCHANGE.size())

Given this limitation, it doesn't seem sensible to only promote to the body on completion.
The only reason I can think of is to limit regression to existing completionPredicates that
expect the first message in {{body}} instead of {{body.get(0)}}. That said, CAMEL-6744 already
introduced this change to the subsequent route.



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

Mime
View raw message