From 41b5680b56daa54e57f5b22fa0ace2079f039240 Mon Sep 17 00:00:00 2001
From: Rossen Stoyanchev <rstoyanchev@vmware.com>
Date: Fri, 29 Oct 2010 08:15:20 +0000
Subject: [PATCH] SWF-360 Update docs for flow managed persistence propagation

---
 .../src/flow-managed-persistence.xml                   | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/spring-webflow-reference/src/flow-managed-persistence.xml b/spring-webflow-reference/src/flow-managed-persistence.xml
index c307c9fb..0f2259cd 100644
--- a/spring-webflow-reference/src/flow-managed-persistence.xml
+++ b/spring-webflow-reference/src/flow-managed-persistence.xml
@@ -75,4 +75,14 @@
 			Such data access operations should always execute non transactionally or in read-only transactions to maintain isolation of intermediate edits.
 		</para>
 	</sect1>
+	<sect1 id="flow-managed-persistence-propagation">
+		<title>Flow Managed Persistence And Sub-Flows</title>
+		<para>
+			Starting with version 2.3 a flow managed <code>PersistenceContext</code> is automatically extended
+			(propagated) to subflows assuming the subflow also has the <code>&lt;perstistence-context/&gt;</code>
+			variable. When a subflow re-uses the <code>PersistenceContext</code> started by its parent it ignores 
+			commit flags when an end state is reached thereby deferring the final decision (to commit or not) to 
+			its parent.
+		</para>
+	</sect1>
 </chapter>
\ No newline at end of file