[
https://issues.apache.org/struts/browse/WW-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wes Wannemacher updated WW-3191:
--------------------------------
Fix Version/s: (was: 2.1.8)
2.1.9
Bumping to 2.1.9... Leaving here since we are going to begin moving xwork into
apache-space, if this does not happen before the next release, we need to fix
this at opensymphony.
> Per Action alias validation for wildcard mappings broken due to WW-2996
> -----------------------------------------------------------------------
>
> Key: WW-3191
> URL: https://issues.apache.org/struts/browse/WW-3191
> Project: Struts 2
> Issue Type: Bug
> Components: Core Interceptors
> Affects Versions: 2.1.7
> Reporter: Peter Phillips
> Fix For: 2.1.9
>
>
> The com.opensymphony.xwork2.ValidationInterceptor was changed as a result of
> WW-2996 so that the name from the struts configuration file is passed into
> the action validation manager instead of the action alias name.
> The com.opensymphony.xwork2.validator.AnnotationActionValidator in
> buildAliasValidatorConfigs then tries to look for a file to load based on the
> config. This should be of the format ActionName-alias-validation.xml but if
> the struts configuration name is a wildcard mapping this will now be
> ActionName-alias*-validation.xml instead.
> So in my example the action alias is newMessage but the ValidationInterceptor
> is passing in new* as the context and then the manager tries to look for a
> file called NewMessage-new*-validation.xml instead of
> NewMessage-newMessage-validation.xml and can't find it.
> If I replace the validation interceptor with the struts 2.1.6 version then
> the validation works as expected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
