From bc498f78be8b20144967315a97b061a9121bfb6e Mon Sep 17 00:00:00 2001
From: Oleg Zhurakousky <ozhurakousky@vmware.com>
Date: Mon, 23 May 2011 19:39:36 -0400
Subject: [PATCH] INT-1912 fixed documentation regarding
 'release-strategy-expression' which has List<Messages> as the root object of
 SpEL Context (not Message)

---
 docs/src/reference/docbook/aggregator.xml | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/src/reference/docbook/aggregator.xml b/docs/src/reference/docbook/aggregator.xml
index 7c33aa5019..5031b58117 100644
--- a/docs/src/reference/docbook/aggregator.xml
+++ b/docs/src/reference/docbook/aggregator.xml
@@ -555,12 +555,14 @@
 	</para>
 	<para>
     Likewise, for the <interfacename>ReleaseStrategy</interfacename> you can implement your release logic via 
-    a SpEL expression and configure it via the <code>release-strategy-expression</code> attribute.
+    a SpEL expression and configure it via the <code>release-strategy-expression</code> attribute. 
+    The only exception is that since ReleaseStrategy is passed the List of Messages the the root object in the SopEL
+    Evaluation context is the List itself which can be referenced as <code>#this</code>.
 	</para>
 	<para>
 	For example:
 
-	<programlisting language="xml"><![CDATA[release-strategy-expression="payload.size() gt 5"]]></programlisting>
+	<programlisting language="xml"><![CDATA[release-strategy-expression="#this.size() gt 5"]]></programlisting>
 	
 	In this example the root object of the SpEL Evaluation Context is the
     <interfacename>MessageGroup</interfacename> itself, and you are simply stating