beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlin Rogers (JIRA)" <...@beehive.apache.org>
Subject [jira] Updated: (BEEHIVE-1144) No validation of form beans in an action with the useFormBean attribute
Date Thu, 07 Sep 2006 16:31:22 GMT
     [ 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

        

Mime
View raw message