AggregationStrategy and wrong sequence order

[Sven Bauhan]

Hi,

I try to implement a fault handling in my AggregationStrategy for 
missing segments or a wrong sequence order.

The standard for my protocol says, when the segments are not received in 
correct order, the receiver shall send an error response and withdraw 
all previously received segments of the message. The sender will send 
the complete message again on error response.

In the method aggregate(Exchange oldExchange, Exchange newExchange) I 
throw an exception. This is caught in the route and an error response is 
sent back. But with the next segment, the oldExchange is unchanged.

What I would expect is that the aggregator discards all messages 
previously received for this correlation key. So the next segment 
received would have an oldExchange=null.

Is it possible to make the aggregator act this way? how can I implement 
this?

Thanks, Sven