You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Steve Hanson (JIRA)" <be...@incubator.apache.org> on 2005/02/02 22:16:18 UTC

[jira] Resolved: (BEEHIVE-81) Page Flow Overview - clarification on form bean classes

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

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

I took out the mention of FormData entirely.  This legacy info just serves to confuse.

We can state the advantages of using FormData in another doc.

> Page Flow Overview - clarification on form bean classes
> -------------------------------------------------------
>
>          Key: BEEHIVE-81
>          URL: http://issues.apache.org/jira/browse/BEEHIVE-81
>      Project: Beehive
>         Type: Improvement
>   Components: Documentation
>     Versions: V1Alpha
>     Reporter: Rich Feit
>     Assignee: Rich Feit
>     Priority: Minor
>      Fix For: V1Beta

>
> At http://incubator.apache.org/beehive/pageflow/pageflow_controllers.html , in the section entitled Handling Forms, we could mention that org.apache.beehive.netui.pageflow.FormData optional as the superclass.  We should also emphasize that form bean classes do *not* have to be inner classes of the page flow.  The page says it "may" be an inner class, but there's been so much confusion about this in the past that I think it would be good to mention it here and nip it in the bud.

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