beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rich Feit (JIRA)" <beehive-...@incubator.apache.org>
Subject [jira] Reopened: (BEEHIVE-76) Page Flow Overview - content about State in page flows
Date Thu, 02 Dec 2004 19:16:39 GMT
     [ 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


Mime
View raw message