Thanks. I'm not sure on whether the current design of the aggregator actually allows for this though? I think the current design is "push" based: an upstream processor "pushes" exchanges into the aggregator; the aggregator's completion mechanism then decides whether to submit or not, yet.
I think my end goal would require a "pull" mechanism (analagous to the receiveNoWait() call from my code sample). Basically I'd need a way to say "dearest upstream exchange deliverer, do you have anything available that I could consume at this point in time? If not I'm going to press ahead, but if you do, I'd like it please". Perhaps something like this does exist, but I've missed it? -- View this message in context: http://camel.465427.n5.nabble.com/Aggregate-up-to-N-ASAP-tp5758134p5758311.html Sent from the Camel - Users mailing list archive at Nabble.com.
