I have implemented my proposed solution from my previous post, and it seems like it will work out. However, performing the aggregation in a separate route is a bit trickier than using an AggregationStrategy on the multicast or recipientList themselves. It doesn't look like any of the headers/properties that allow Camel to correlate the responses in the AggregationStrategy are available when the aggregation is done on a separate route. I was hoping to be able to use Camel-supplied correlation ID and indexes/counts to make the aggregation seamless, but I've resorted to adding my own headers for this.
Is anyone else doing aggregation in a route separate from the route with the recipientList or multicast? Have you found an easier way to aggregate than what I'm currently doing? -- View this message in context: http://camel.465427.n5.nabble.com/Is-there-an-alternative-to-request-reply-when-you-want-to-use-JMS-transactions-tp5747691p5747962.html Sent from the Camel - Users mailing list archive at Nabble.com.
