From 808c447f91ed86b15ec019c12f3505e5cb1acf86 Mon Sep 17 00:00:00 2001
From: Keith Donald <kdonald@vmware.com>
Date: Thu, 1 Mar 2007 14:08:35 +0000
Subject: [PATCH] removed note about continuations

---
 .../sellitem-jsf/src/main/webapp/intro.jsp    | 29 -------------------
 1 file changed, 29 deletions(-)

diff --git a/spring-webflow-samples/sellitem-jsf/src/main/webapp/intro.jsp b/spring-webflow-samples/sellitem-jsf/src/main/webapp/intro.jsp
index 00786e8a..a145fe49 100644
--- a/spring-webflow-samples/sellitem-jsf/src/main/webapp/intro.jsp
+++ b/spring-webflow-samples/sellitem-jsf/src/main/webapp/intro.jsp
@@ -39,35 +39,6 @@
 						Using <A href="http://www.ognl.org/">OGNL</A> based conditional expressions.
 					</LI>
 				</UL>
-				<UL>
-					<LI>
-						Note on continuations: The original sellitem sample shows 
-						continuations in use, in the words of the intro, "Using
-						continuations to make the flow completely stable, no matter
-						how browser navigation buttons are used."<br/>
-						This JSF version of sellitem is currently set to use normal
-						session storage.<br/>
-						The JSF Web Flow integration does support the continuation storages.
-						However, because JSF page components themselves have internal state,
-						it is not enough for Web Flow to be using continuation storage, the
-						JSF engine itself must be configured to use client-side or server-side
-						continuation style storage for the component state, instead of the
-						normal shared, Session based storage. We have not yet investigated
-						how to set MyFaces or the JSR RI to use client side storage, but
-						it is theoretically possible at least to the extent that the JSF
-						specification talks about JSF implementations offering it as an
-						<em>option</em>. We have seen no discussion of server-side continuation-
-						style storage for JSF component state<br/>
-						If you do configure your JSF engine for client-side storage of 
-						component state, and set Web Flow to use client side continuation
-						storage it does mean that pages can not trigger the auto-creation of
-						flow variables on demand since the flow execution id needs to be known
-						to the page, and the id _is_ the storage for the flow state, a classic
-						chicken and egg situation. Just make sure any flow-scoped variables
-						are created ahead of time in the flow, before any JSF page component
-						tried to reference them.
-					</LI>
-				</UL>
 			</P>
 		</DIV>