[ http://issues.apache.org/jira/browse/BEEHIVE-76?page=history ]
Steve Hanson resolved BEEHIVE-76:
---------------------------------
Resolution: Fixed
The text now reads:
"
When a user enters a Page Flow (by calling an URL in the Page Flow's URL
space), an instance of the
Page Flow's controller class is created. While the user is in
the Page Flow, the controller class
stores the accumulated flow-related state in member variables
of the conroller class.
The methods within the class have access to the
accumulated state, making for easy state management within the
web application. For example,
suppose your web application calls for a multi-page
registration, where the user moves from page to
page filling out a user profile. The controller class stores
the user data as the user progresses
through the registration and has access to the profile data as
session state. When the user leaves
the Page Flow, the state is automatically cleaned up.
"
> Page Flow Overview - content about State in page flows
> ------------------------------------------------------
>
> Key: BEEHIVE-76
> URL: http://issues.apache.org/jira/browse/BEEHIVE-76
> Project: Beehive
> Type: Improvement
> Components: Documentation
> Versions: V1Alpha
> Reporter: Rich Feit
> Assignee: Steve Hanson
> Fix For: V1Alpha
>
> An important piece of the pie is the fact that page flows are stateful --
> when a user "hits" a page flow, an instance is created. While the user is
> "in" the page flow, action methods (and exception handler methods) have
> access to the member state, and when the user "leaves" the page flow for
> another one, the local state is cleaned up. This doesn't have to be a big
> session, but mentioning it with an example would be nice.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
