beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Russ Baker (JIRA)" <j...@apache.org>
Subject [jira] Updated: (BEEHIVE-1144) No validation of form beans in an action with the useFormBean attribute
Date Mon, 25 Jun 2007 17:32:26 GMT

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


Mime
View raw message