From 3db1aabd4c1642ce18d9bfe53ded7d06528a0ab8 Mon Sep 17 00:00:00 2001
From: Keith Donald <kdonald@vmware.com>
Date: Fri, 25 Apr 2008 00:56:47 +0000
Subject: [PATCH] addressed cyclical dependency with view package

---
 spring-webflow-reference/src/flow-managed-persistence.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spring-webflow-reference/src/flow-managed-persistence.xml b/spring-webflow-reference/src/flow-managed-persistence.xml
index 56ecc24f..36ba350c 100644
--- a/spring-webflow-reference/src/flow-managed-persistence.xml
+++ b/spring-webflow-reference/src/flow-managed-persistence.xml
@@ -77,7 +77,7 @@
 		</para>
 		<para>
 			That is it.  When your flow starts, the listener will handle allocating a new <code>EntityManager</code> in <code>flowScope</code>.
-			Reference this EntityManager at anytime from within your flow by using the special <code>entityManager</code> variable.
+			Reference this EntityManager at anytime from within your flow by using the special <code>persistenceContext</code> variable.
 			In addition, any data access that occurs using a Spring managed data access object will use this EntityManager automatically.
 			Such data access operations should always execute non transactionally or in read-only transactions to maintain isolation of intermediate edits.
 		</para>