|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
|
|
[jira] Created: (WW-3191) Per Action alias validation for wildcard mappings broken due to WW-2996Per 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 Priority: Minor 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. |
|
|
[jira] Updated: (WW-3191) Per Action alias validation for wildcard mappings broken due to WW-2996[ https://issues.apache.org/struts/browse/WW-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ville Saalo updated WW-3191: ---------------------------- Priority: Major (was: Minor) Where I work this bug basically prevents any validators from working at all so I'd call this one a major instead of a minor bug. > 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 > > 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. |
|
|
[jira] Updated: (WW-3191) Per Action alias validation for wildcard mappings broken due to WW-2996[ 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: 2.1.8 this sounds bad, I'll try to get it fixed for 2.1.8 > 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.8 > > > 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. |
|
|
[jira] Updated: (WW-3191) Per Action alias validation for wildcard mappings broken due to WW-2996[ 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. |
|
|
[jira] Commented: (WW-3191) Per Action alias validation for wildcard mappings broken due to WW-2996[ https://issues.apache.org/struts/browse/WW-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47025#action_47025 ] Musachy Barroso commented on WW-3191: ------------------------------------- is this still a problem? I thought this had been fixed > 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.8 > 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. |
|
|
[jira] Resolved: (WW-3191) Per Action alias validation for wildcard mappings broken due to WW-2996[ https://issues.apache.org/struts/browse/WW-3191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Musachy Barroso resolved WW-3191. --------------------------------- Resolution: Fixed Fix Version/s: (was: 2.1.9) 2.1.8.1 fixed in xwork rv2037 > 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.8 > Reporter: Peter Phillips > Fix For: 2.1.8.1 > > > 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. |
| Free embeddable forum powered by Nabble | Forum Help |