From 86d43fd898daf62b2e4a88350ed8bdbe857092e7 Mon Sep 17 00:00:00 2001 From: Mark Fisher Date: Fri, 26 Aug 2011 17:55:03 -0400 Subject: [PATCH] polishing --- docs/src/reference/docbook/aggregator.xml | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/src/reference/docbook/aggregator.xml b/docs/src/reference/docbook/aggregator.xml index ee6752c08a..4803064b41 100644 --- a/docs/src/reference/docbook/aggregator.xml +++ b/docs/src/reference/docbook/aggregator.xml @@ -234,24 +234,24 @@ For example: - >){..} + public boolean canMessagesBeReleased(List>) {...} }]]> -){..} + public boolean canMessagesBeReleased(List) {...} }]]> -As you can see based on the above signatures the POJO-based Release Strategy will be passed a Collection of unmarked Messages +As you can see based on the above signatures, the POJO-based Release Strategy will be passed a Collection of unmarked Messages if you need access to the whole Message or Collection of payload objects if the type parameter is -anything other than Message. Typically this would satisfy the majority of the use cases. However if -you need complete access to the MessageGroup which gives you access to unmarked and marked Messages -than provide the implementation of the ReleaseStrategy. +anything other than Message. Typically this would satisfy the majority of use cases. However if +for some reason you need to access the full MessageGroup - which contains unmarked and marked Messages - +then you should simply provide an implementation of the ReleaseStrategy interface. When the group is released for aggregation, all its unmarked