From ef915ac10b76203ff9ff075295bac5bfbe215d63 Mon Sep 17 00:00:00 2001 From: Keith Donald Date: Mon, 10 Nov 2008 20:05:35 +0000 Subject: [PATCH] conversation to flow --- spring-webflow-reference/src/flow-managed-persistence.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/spring-webflow-reference/src/flow-managed-persistence.xml b/spring-webflow-reference/src/flow-managed-persistence.xml index c6182a2b..26425a85 100644 --- a/spring-webflow-reference/src/flow-managed-persistence.xml +++ b/spring-webflow-reference/src/flow-managed-persistence.xml @@ -23,8 +23,8 @@ uses that context for data access during the course of flow execution, and commits changes made to persistent entities at the end. This pattern provides isolation of intermediate edits by only committing changes to the database at the end of flow execution. This pattern is often used in conjunction with an optimistic locking strategy to protect the integrity of data modified in parallel by multiple users. - To support saving and restarting the progress of a flow over an extended period of time, a durable store for conversational state must be used. - If a save and restart capability is not required, standard HTTP session-based storage of conversational state is sufficient. + To support saving and restarting the progress of a flow over an extended period of time, a durable store for flow state must be used. + If a save and restart capability is not required, standard HTTP session-based storage of flow state is sufficient. In that case, session expiration or termination before commit could potentially result in changes being lost.