Related to the Aggregator, albeit different from a functional standpoint, is the Resequencer.

The Resequencer works in a similar way to the Aggregator, in the sense that it uses the CORRELATION_ID to store messages in groups, the difference being that the Resequencer does not process the messages in any way. It simply releases them in the order of their SEQUENCE_NUMBER header values. With respect to that, the user might opt to release all messages at once (after the whole sequence, according to the SEQUENCE_SIZE, has been released), or as soon as a valid sequence is available.

Configuring a resequencer requires only including the appropriate element in XML. A sample resequencer configuration is shown below. ]]> The id of the resequencer is optional. The input channel of the resequencer. Required. The channel where the resequencer will send the reordered messages. Optional. The channel where the resequencer will send the messages that timed out (if send-partial-result-on-timeout is false). Optional. Whether to send out ordered sequences as soon as they are available, or only after the whole message group arrives. Optional (false by default). If this flag is not specified (so a complete sequence is defined by the sequence headers) then it can make sense to provide a custom Comparator to be used to order the messages when sending (use the XML attribute comparator to point to a bean definition). If release-partial-sequences is true then there is no way with a custom comparator to define a partial sequence. To do that you would have to provide a release-strategy (also a reference to another bean definition, either a POJO or a ReleaseStrategy ). A reference to a MessageGroupStore that can be used to store groups of messages under their correlation key until they are complete. Optional with default a volatile in-memory store. Whether, upon the expiration of the group, the ordered group should be sent out (even if some of the messages are missing). Optional (false by default). See . The timeout for sending out messages. Optional. Since there is no custom behavior to be implemented in Java classes for resequencers, there is no annotation support for it.