You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by "Carlin Rogers (JIRA)" <de...@beehive.apache.org> on 2006/09/07 18:20:24 UTC
[jira] Created: (BEEHIVE-1144) No validation of form beans in an
action with the useFormBean attribute
No validation of form beans in an action with the useFormBean attribute
-----------------------------------------------------------------------
Key: BEEHIVE-1144
URL: http://issues.apache.org/jira/browse/BEEHIVE-1144
Project: Beehive
Issue Type: Bug
Components: NetUI
Affects Versions: 1.0.1, v.next
Reporter: Carlin Rogers
Fix For: v.next
I noticed in a sample I had that validation for a form bean for an action with the useFormBean property fails to execute. The commons validator code fails to get the form bean for the form bean name. This may be due to a discrepency in the names of the form. When the action includes the useFormBean attribute, the compiler generates the struts module config with both a <form-bean> of the desired name and a second one with the "_nonFlowScoped" suffix. Seems like the vlaidator does not get the correct element from the struts module config file to match the name of the form bean.
--
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
[jira] Updated: (BEEHIVE-1144) No validation of form beans in an
action with the useFormBean attribute
Posted by "Carlin Rogers (JIRA)" <de...@beehive.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-1144?page=all ]
Carlin Rogers updated BEEHIVE-1144:
-----------------------------------
Attachment: j1144-test.zip
attaching a test case that can be used to repro the bug.
> No validation of form beans in an action with the useFormBean attribute
> -----------------------------------------------------------------------
>
> Key: BEEHIVE-1144
> URL: http://issues.apache.org/jira/browse/BEEHIVE-1144
> Project: Beehive
> Issue Type: Bug
> Components: NetUI
> Affects Versions: 1.0.1, v.next
> Reporter: Carlin Rogers
> Fix For: v.next
>
> Attachments: j1144-test.zip
>
>
> I noticed in a sample I had that validation for a form bean for an action with the useFormBean property fails to execute. The commons validator code fails to get the form bean for the form bean name. This may be due to a discrepency in the names of the form. When the action includes the useFormBean attribute, the compiler generates the struts module config with both a <form-bean> of the desired name and a second one with the "_nonFlowScoped" suffix. Seems like the vlaidator does not get the correct element from the struts module config file to match the name of the form bean.
--
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
[jira] Resolved: (BEEHIVE-1144) No validation of form beans in an
action with the useFormBean attribute
Posted by "Carlin Rogers (JIRA)" <de...@beehive.apache.org>.
[ http://issues.apache.org/jira/browse/BEEHIVE-1144?page=all ]
Carlin Rogers resolved BEEHIVE-1144.
------------------------------------
Resolution: Fixed
Assignee: Julie Zhuo
This is fixed with SVN revision 446518...
http://svn.apache.org/viewvc?rev=446518&view=rev
> No validation of form beans in an action with the useFormBean attribute
> -----------------------------------------------------------------------
>
> Key: BEEHIVE-1144
> URL: http://issues.apache.org/jira/browse/BEEHIVE-1144
> Project: Beehive
> Issue Type: Bug
> Components: NetUI
> Affects Versions: 1.0.1, v.next
> Reporter: Carlin Rogers
> Assigned To: Julie Zhuo
> Fix For: v.next
>
> Attachments: j1144-test.zip
>
>
> I noticed in a sample I had that validation for a form bean for an action with the useFormBean property fails to execute. The commons validator code fails to get the form bean for the form bean name. This may be due to a discrepency in the names of the form. When the action includes the useFormBean attribute, the compiler generates the struts module config with both a <form-bean> of the desired name and a second one with the "_nonFlowScoped" suffix. Seems like the vlaidator does not get the correct element from the struts module config file to match the name of the form bean.
--
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
[jira] Updated: (BEEHIVE-1144) No validation of form beans in an
action with the useFormBean attribute
Posted by "Russ Baker (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BEEHIVE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Russ Baker updated BEEHIVE-1144:
--------------------------------
I verified that the validator does get called with the useFormBean and properly validates the form. I validated this using Carlin's example and verified against SVN 549584. I recommend that this bug be closed.
> No validation of form beans in an action with the useFormBean attribute
> -----------------------------------------------------------------------
>
> Key: BEEHIVE-1144
> URL: https://issues.apache.org/jira/browse/BEEHIVE-1144
> Project: Beehive
> Issue Type: Bug
> Components: NetUI
> Affects Versions: 1.0.1, 1.0.2
> Reporter: Carlin Rogers
> Assignee: Julie Zhuo
> Fix For: 1.0.2
>
> Attachments: j1144-test.zip
>
>
> I noticed in a sample I had that validation for a form bean for an action with the useFormBean property fails to execute. The commons validator code fails to get the form bean for the form bean name. This may be due to a discrepency in the names of the form. When the action includes the useFormBean attribute, the compiler generates the struts module config with both a <form-bean> of the desired name and a second one with the "_nonFlowScoped" suffix. Seems like the vlaidator does not get the correct element from the struts module config file to match the name of the form bean.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (BEEHIVE-1144) No validation of form beans in an
action with the useFormBean attribute
Posted by "Julie Zhuo (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BEEHIVE-1144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julie Zhuo closed BEEHIVE-1144.
-------------------------------
Thanks Russ. Close.
> No validation of form beans in an action with the useFormBean attribute
> -----------------------------------------------------------------------
>
> Key: BEEHIVE-1144
> URL: https://issues.apache.org/jira/browse/BEEHIVE-1144
> Project: Beehive
> Issue Type: Bug
> Components: NetUI
> Affects Versions: 1.0.1, 1.0.2
> Reporter: Carlin Rogers
> Assignee: Julie Zhuo
> Fix For: 1.0.2
>
> Attachments: j1144-test.zip
>
>
> I noticed in a sample I had that validation for a form bean for an action with the useFormBean property fails to execute. The commons validator code fails to get the form bean for the form bean name. This may be due to a discrepency in the names of the form. When the action includes the useFormBean attribute, the compiler generates the struts module config with both a <form-bean> of the desired name and a second one with the "_nonFlowScoped" suffix. Seems like the vlaidator does not get the correct element from the struts module config file to match the name of the form bean.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.