[
https://issues.apache.org/jira/browse/WW-4139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707880#comment-13707880
]
Hudson commented on WW-4139:
----------------------------
SUCCESS: Integrated in Struts2-JDK6 #749 (See
[https://builds.apache.org/job/Struts2-JDK6/749/])
WW-4139 Reverts client side validation to old behaviour (lukaszlenart: rev
1502429)
*
/struts/struts2/trunk/core/src/main/java/org/apache/struts2/components/Form.java
> 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
> Assignee: Lukasz Lenart
> 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
