On Sun, Aug 30, 2009 at 3:55 AM, huntc<hu...@mac.com> wrote: > > Many apologies - I found the problem. I thought that I was checking to see if > the old exchange was null in my aggregation strategy. I was actually > checking the body of the old exchange for null and thus a null pointer > exception must have been thrown somewhere. > --
Glad you got it working as I was really wondering what could have happened as we got tons of unit tests. But yeah the AggregationStrategy has been changed to provide the "result" in the IN message. I do hope we get around the time in the future to allow a POJO for aggregation as it would be easier to work with instead of low level Exchange. > View this message in context: > http://www.nabble.com/Aggregator-not-working-for-me-in-2.0-tp25202246p25207993.html > Sent from the Camel - Users (activemq) mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
