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:40:23 UTC
[jira] Created: (BEEHIVE-81) Page Flow Overview - clarification on form bean classes
Page Flow Overview - clarification on form bean classes
-------------------------------------------------------
Key: BEEHIVE-81
URL: http://nagoya.apache.org/jira/browse/BEEHIVE-81
Project: Beehive
Type: Improvement
Components: Documentation
Versions: V1Alpha
Reporter: Rich Feit
Assigned to: Steve Hanson
Priority: Minor
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://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] Resolved: (BEEHIVE-81) Page Flow Overview - clarification on form bean classes
Posted by "Steve Hanson (JIRA)" <be...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/BEEHIVE-81?page=history ]
Steve Hanson resolved BEEHIVE-81:
---------------------------------
Assign To: (was: Steve Hanson)
Resolution: Fixed
Fix Version: V1Alpha
I changed the text to read:
"
First, define a JavaBean to represent the HTML form to be submitted. This JavaBean can be of any Java type. (In Struts applications the JavaBean must be a subclass of org.apache.struts.action.ActionForm. Similarly, in earlier incarnations of Page Flows the JavaBean had to be a subclass of org.apache.beehive.netui.pageflow.FormData. But this restriction has been loosened in the current incarnation: the JavaBean representation may be any JavaBean type.)
The JavaBean may be defined (1) as a static inner class of the controller itself (see example below) or (2) as a stand-alone Java class in a separate file. The JavaBean class follows normal JavaBean conventions and require no special annotations. The JavaBean shown below is a subclass of FormData, but this is not a requirement. The JavaBean can be of any type.
"
> Page Flow Overview - clarification on form bean classes
> -------------------------------------------------------
>
> Key: BEEHIVE-81
> URL: http://nagoya.apache.org/jira/browse/BEEHIVE-81
> Project: Beehive
> Type: Improvement
> Components: Documentation
> Versions: V1Alpha
> Reporter: Rich Feit
> Priority: Minor
> Fix For: V1Alpha
>
> 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://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-81) Page Flow Overview - clarification on form bean classes
Posted by "Rich Feit (JIRA)" <be...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/BEEHIVE-81?page=history ]
Rich Feit reopened BEEHIVE-81:
------------------------------
Assign To: Steve Hanson
You bring up an excellent point -- I'm reopening this just so it doesn't get lost. There are two small advantages to using FormData:
1) To do complex validation logic, you can simply override the validate() method (with a non-FormData bean you also have to implement org.apache.beehive.netui.pageflow.Validatable).
2) There's slightly less overhead, since we don't have to wrap the bean in an ActionForm internally.
It's up to you whether we should mention it at this point in the overview. If not, just re-resolve...
> Page Flow Overview - clarification on form bean classes
> -------------------------------------------------------
>
> Key: BEEHIVE-81
> URL: http://nagoya.apache.org/jira/browse/BEEHIVE-81
> Project: Beehive
> Type: Improvement
> Components: Documentation
> Versions: V1Alpha
> Reporter: Rich Feit
> Assignee: Steve Hanson
> Priority: Minor
> Fix For: V1Alpha
>
> 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://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] Resolved: (BEEHIVE-81) Page Flow Overview - clarification on form bean classes
Posted by "Steve Hanson (JIRA)" <be...@incubator.apache.org>.
[ 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
[jira] Commented: (BEEHIVE-81) Page Flow Overview - clarification on form bean classes
Posted by "Jeremiah Johnson (JIRA)" <be...@incubator.apache.org>.
[ http://nagoya.apache.org/jira/browse/BEEHIVE-81?page=comments#action_56479 ]
Jeremiah Johnson commented on BEEHIVE-81:
-----------------------------------------
For the purpose of the overview, the FormData should be pulled from LoginForm. More detailed documentation should go over the value of extending FormData, but as it is the use looks contradictory to the text (which says FormData isn't necessary).
> Page Flow Overview - clarification on form bean classes
> -------------------------------------------------------
>
> Key: BEEHIVE-81
> URL: http://nagoya.apache.org/jira/browse/BEEHIVE-81
> Project: Beehive
> Type: Improvement
> Components: Documentation
> Versions: V1Alpha
> Reporter: Rich Feit
> Assignee: Steve Hanson
> Priority: Minor
> Fix For: V1Alpha
>
> 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://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-81) Page Flow Overview - clarification on form bean classes
Posted by "Nathan Jantz (JIRA)" <be...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-81?page=all ]
Nathan Jantz closed BEEHIVE-81:
-------------------------------
Assign To: Nathan Jantz (was: Rich Feit)
Verified in 1.0m1-rc2.
> 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: Nathan Jantz
> 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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira