diff --git a/docs/src/reference/docbook/aggregator.xml b/docs/src/reference/docbook/aggregator.xml index 3199881200..5d4f7fecc3 100644 --- a/docs/src/reference/docbook/aggregator.xml +++ b/docs/src/reference/docbook/aggregator.xml @@ -637,8 +637,37 @@ that the components (whether defined by the framework or a user) should be able to remain stateless. All state is carried by the MessageGroup and its management is delegated to the - MessageGroupStore. + MessageGroupStore. + + + message); + + MessageGroup markMessageGroup(MessageGroup group); + + MessageGroup removeMessageFromGroup(Object key, Message messageToRemove); + + MessageGroup markMessageFromGroup(Object key, Message messageToMark); + + void removeMessageGroup(Object groupId); + + void registerMessageGroupExpiryCallback(MessageGroupCallback callback); + + int expireMessageGroups(long timeout); +}]]> + + For more information on regarding details for each method please refer to + javadoc http://static.springsource.org/spring-integration/api/org/springframework/integration/store/MessageGroupStore.html + + The MessageGroupStore accumulates state information in MessageGroups while waiting for a release strategy to be triggered, and that event might not ever happen. @@ -662,11 +691,6 @@ applies, on demand, to all messages whose timestamp is earlier than a time supplied as a parameter: - - The expireMessageGroups method can be called with a timeout value: any message older than the current time minus this value will be expired, and have the callbacks applied. Thus it is the user of the store that