You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Krista Baker (JIRA)" <be...@incubator.apache.org> on 2005/05/20 01:33:54 UTC
[jira] Closed: (BEEHIVE-361) Redundant form-bean type information in generated Struts XML when form class extends ActionForm
[ http://issues.apache.org/jira/browse/BEEHIVE-361?page=all ]
Krista Baker closed BEEHIVE-361:
--------------------------------
Verified at svn revision 170952 that with the repro, the redundant form-bean type information for the non-ActionForm extended bean does not show up in the struts xml file.
> Redundant form-bean type information in generated Struts XML when form class extends ActionForm
> -----------------------------------------------------------------------------------------------
>
> Key: BEEHIVE-361
> URL: http://issues.apache.org/jira/browse/BEEHIVE-361
> Project: Beehive
> Type: Bug
> Components: NetUI
> Versions: V1Beta
> Reporter: Rich Feit
> Assignee: Krista Baker
> Priority: Minor
> Fix For: V1Beta
>
> Consider the following two form beans:
> package test;
> public class Form1 extends ActionForm
> {
> }
> package test;
> public class Form2
> {
> }
> In a page flow that uses these two form beans, you get the following two form-bean elements in the generated Struts XML:
> <form-bean name="form1" type="org.apache.beehive.netui.pageflow.internal.AnyBeanActionForm" className="org.apache.beehive.netui.pageflow.config.PageFlowActionFormBean">
> <set-property property="actualType" value="test.Form1"/>
> </form-bean>
> <form-bean name="form2" type="test.Form2" className="org.apache.beehive.netui.pageflow.config.PageFlowActionFormBean">
> <set-property property="actualType" value="test.Form2"/>
> </form-bean>
> In the second form-bean, the "actualType" custom property is unnecessary; the runtime should be able to use the type attribute in a normal form-bean:
> <form-bean name="form2" type="test.Form2"/>
> This isn't a vital issue, but it is causing clutter in the generated Struts XML, and the fix is easy...
--
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