You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Wes Wannemacher (JIRA)" <ji...@apache.org> on 2009/04/16 19:12:06 UTC

[jira] Commented: (WW-2975) client side validation and components with forms

    [ https://issues.apache.org/struts/browse/WW-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45986#action_45986 ] 

Wes Wannemacher commented on WW-2975:
-------------------------------------

Dave, I'm too lazy to look around and see if your hack is in place... If so, is it enough to close this issue? 

> client side validation and components with forms
> ------------------------------------------------
>
>                 Key: WW-2975
>                 URL: https://issues.apache.org/struts/browse/WW-2975
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Other
>    Affects Versions: 2.1.6
>            Reporter: Miguel Diaz
>
> When form-close-validate.ftl generates the JavaScript validation code, it only takes into account the fields that are present in the <s:form> when it's processed (via parameters.tagNames).
> There are two problems with this:
> - if for some reason a field is missing, the validation will fail but no message will be displayed
> - if one creates a <s:component> that builds a form and gets some fields passed to it in a parameter (i.e. receives the HTML generated by some fields) then the form doesn't know about the fields so they aren't included in the "tagNames" parameter, thus not taken into account for the JavaScript validation

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.