[
https://issues.apache.org/struts/browse/WW-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46676#action_46676
]
Wes Wannemacher commented on WW-3194:
-------------------------------------
There are snapshots in a few places, if you go here -
http://hudson.zones.apache.org/hudson/view/Struts/job/xwork2/
and dig down, you'll find this link -
http://hudson.zones.apache.org/hudson/view/Struts/job/xwork2/73/com.opensymphony$xwork-core/artifact/com.opensymphony/xwork-core/2.1.6-SNAPSHOT/xwork-core-2.1.6-SNAPSHOT.jar
Which will get you xwork-core 2.1.6-SNAPSHOT
> Can no longer have seperate xml validations for different action methods
> mapped with a wildcard
> -----------------------------------------------------------------------------------------------
>
> Key: WW-3194
> URL: https://issues.apache.org/struts/browse/WW-3194
> Project: Struts 2
> Issue Type: Bug
> Components: XML Validators
> Affects Versions: 2.1.7
> Reporter: Jasper Rosenberg
> Priority: Blocker
> Fix For: 2.1.8
>
>
> It used to be that if I had an action with two methods, say delete() and
> save(), then I could map a separate them with a single action like so:
> <action name="*Review" class="com.myCompany.ReviewAction" method="{1}">
> <result name="success">review.ftl</result>
> </action>
> And then have separate validation files for each method like so:
> ReviewAction-deleteReview-validation.xml
> ReviewAction-saveReview-validation.xml
> Unfortunately, this has been broken by this issue:
> https://issues.apache.org/struts/browse/WW-2996
> as it appears to now look by the wildcard name "*Review" rather than the
> action name "deleteReview" or "saveReview" when looking for validation files.
> Perhaps what needs to happen is that the context should go back to being the
> action name (deleteReview or saveReview), but the key to the validator cache
> should be the config name + the method (in this case if we use | as a
> separator "*Review|save" and "*Review|delete". This would mean for my case
> I'd get two validators and two cached instances, but for the person with the
> issue in WW-2996, since they have a non-dynamic method, they would get only
> the single validator cached.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
