You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Rich Feit (JIRA)" <be...@incubator.apache.org> on 2004/11/11 02:19:23 UTC
[jira] Created: (BEEHIVE-76) Page Flow Overview - content about State in page flows
Page Flow Overview - content about State in page flows
------------------------------------------------------
Key: BEEHIVE-76
URL: http://nagoya.apache.org/jira/browse/BEEHIVE-76
Project: Beehive
Type: Improvement
Components: Documentation
Versions: V1Alpha
Reporter: Rich Feit
Assigned to: Steve Hanson
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://nagoya.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
[jira] Closed: (BEEHIVE-76) Page Flow Overview - content about State in page flows
Posted by "Nathan Jantz (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-76?page=all ]
Nathan Jantz closed BEEHIVE-76:
-------------------------------
Assign To: Nathan Jantz (was: Rich Feit)
Verified in 1.0m1-rc2.
> 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: Nathan Jantz
> 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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (BEEHIVE-76) Page Flow Overview - content about State in page flows
Posted by "Steve Hanson (JIRA)" <be...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/BEEHIVE-76?page=history ]
Steve Hanson resolved BEEHIVE-76:
---------------------------------
Assign To: (was: Steve Hanson)
Resolution: Fixed
Fix Version: V1Alpha
Take a look at the "Page Flows are Stateful" seciton in http://incubator.apache.org/beehive/pageflow/pageflow_overview.html
> Page Flow Overview - content about State in page flows
> ------------------------------------------------------
>
> Key: BEEHIVE-76
> URL: http://nagoya.apache.org/jira/browse/BEEHIVE-76
> Project: Beehive
> Type: Improvement
> Components: Documentation
> Versions: V1Alpha
> Reporter: Rich Feit
> 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://nagoya.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
[jira] Reopened: (BEEHIVE-76) Page Flow Overview - content about State in page flows
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/BEEHIVE-76?page=history ]
Rich Feit reopened BEEHIVE-76:
------------------------------
Assign To: Steve Hanson
Minor change... this section says "the controller class stores the accumulated session and user state", but it's not really "accumulated session state" that's being stored. To avoid confusion about HttpSession state and Page Flow state, I think we could say something like "the controller class stores flow-related state in member variables."
> Page Flow Overview - content about State in page flows
> ------------------------------------------------------
>
> Key: BEEHIVE-76
> URL: http://nagoya.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://nagoya.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
[jira] Assigned: (BEEHIVE-76) Page Flow Overview - content about State in page flows
Posted by "Steve Hanson (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-76?page=history ]
Steve Hanson reassigned BEEHIVE-76:
-----------------------------------
Assign To: Rich Feit (was: Steve Hanson)
> 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: Rich Feit
> 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
[jira] Resolved: (BEEHIVE-76) Page Flow Overview - content about State in page flows
Posted by "Steve Hanson (JIRA)" <be...@incubator.apache.org>.
[ 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