[
https://issues.apache.org/struts/browse/WW-2191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42217
]
Ted Husted commented on WW-2191:
--------------------------------
I just noticed a side-effect of setting validateAnnotatedMethodOnly to true is
that it also bypasses property annotations made to methods in a base class.
The problem here is that a useful strategy is to put "format" property
validations on a base class, and then required and conditional validations on
the action methods. So, I guess were looking for
validateAnnotatedActionMethodOnly, but still validation any and all property
validatons.
-Ted.
> Make validateAnnotatedMethodOnly the default and support client-side
> method-only validations
> --------------------------------------------------------------------------------------------
>
> Key: WW-2191
> URL: https://issues.apache.org/struts/browse/WW-2191
> Project: Struts 2
> Issue Type: Improvement
> Components: Validation
> Reporter: Ted Husted
> Fix For: 2.1.x
>
>
> A common use case for validation annotations is to use different validations
> per action method. However, in 2.0.x, the default is to combine the
> validations. A better default would be "true".
> <interceptor-ref name="validation">
> <param
> name="validateAnnotatedMethodOnly">true</param>
> <param
> name="excludeMethods">input,back,cancel,browse</param>
> </interceptor-ref>
> Also, per-method client-side validation does not seem to be supported.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
