Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Date: Wed, 29 Feb 2012 16:21:02 -0800 (PST)
From: wattsc3 <christopher.watts@anz.com>
To: users@camel.apache.org
Message-ID: <1330561262790-5526447.post@n5.nabble.com>
Subject: GroupedExchangeAggregationStrategy not working with HawtDB
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I'd been bashing my head against the wall trying to get the default
aggregator (GroupedExchangeAggregationStrategy) working with HawtDB
aggregator repo, trying to work out why the exchange came out had no
properties until I found this on the help page.
/"And it only persists the Message body and the Message headers. The
Exchange properties are not persisted."
/

Give than GroupedExchangeAggregationStrategy does it by:
/  "Aggregate all exchanges into a single combined Exchange holding all the
aggregated exchanges in a java.util.List as a exchange property with the key
org.apache.camel.Exchange.GROUPED_EXCHANGE."/

So the question is, if these are the preferred solutions for aggregating why
don't they work together. Does everyone just write their own aggregation
strategy to store the list in the body instead of as a property?

We need the persistence so the messages are recoverable.

--
View this message in context: http://camel.465427.n5.nabble.com/GroupedExchangeAggregationStrategy-not-working-with-HawtDB-tp5526447p5526447.html
Sent from the Camel - Users mailing list archive at Nabble.com.