You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/07/12 07:46:05 UTC

[jira] [Commented] (WW-4139) Validation of non-default methods not being executed

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

ASF subversion and git services commented on WW-4139:
-----------------------------------------------------

Commit 1502429 from [~lukaszlenart]
[ https://svn.apache.org/r1502429 ]

WW-4139 Reverts client side validation to old behaviour
                
> Validation of non-default methods not being executed
> ----------------------------------------------------
>
>                 Key: WW-4139
>                 URL: https://issues.apache.org/jira/browse/WW-4139
>             Project: Struts 2
>          Issue Type: Bug
>    Affects Versions: 2.3.15
>            Reporter: Bruno Klava
>             Fix For: 2.3.16
>
>
> Code sample: https://github.com/bklava/struts
> In the example, in the index action/page, there are 2 forms: the difference is that the form 1 submits to the action without setting a method (then calling the default execute() method), while the form 2 submits to the same action but calling a specific method.
> The validator is set annotating the field setter method, so it should be available either to the default execute method and to the non-default method. This is exactly the behaviour obtained when using Struts 2.3.14.3.
> After switching to Struts 2.3.15, the form 2 validation is not executed at all.
> As far as I can tell, this difference is due to changes made in org.apache.struts2.components.Form.getValidators(String name)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira