[jira] Resolved: (BEEHIVE-75) Page Flow Overview - additional reasons/motivations for using Page Flow

["Steve Hanson (JIRA)" <be...@incubator.apache.org>]

     [ http://nagoya.apache.org/jira/browse/BEEHIVE-75?page=history ]
     
Steve Hanson resolved BEEHIVE-75:
---------------------------------

      Assign To:     (was: Steve Hanson)
     Resolution: Fixed
    Fix Version: V1Alpha

Take a look at the "Page Flows are Modular" section in http://incubator.apache.org/beehive/pageflow/pageflow_overview.html

> Page Flow Overview - additional reasons/motivations for using Page Flow
> -----------------------------------------------------------------------
>
>          Key: BEEHIVE-75
>          URL: http://nagoya.apache.org/jira/browse/BEEHIVE-75
>      Project: Beehive
>         Type: Improvement
>   Components: Documentation
>     Versions: V1Alpha
>     Reporter: Rich Feit
>      Fix For: V1Alpha

>
> The Page Flow Overview at http://incubator.apache.org/beehive/pageflow/pageflow_overview.html should at mention some of the main motivations for Page Flow: 
>     1) centralization of Controller logic, state, and metadata
>     2) self-contained pieces of a web application
>     3) reusable flows (nested page flows)
> I don't think it has to go into depth on #3, but it would be nice to have a diagram or blurb about this (some bit of what's at http://dev2dev.bea.com/products/wlworkshop81/articles/pg_flows.jsp , maybe).

-- 
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