You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@struts.apache.org by "Wes Wannemacher (JIRA)" <ji...@apache.org> on 2008/02/25 02:43:11 UTC

[jira] Resolved: (WW-2265) Modify MethodFilterInterceptor to support wildcard method names in the include/exclude lists

     [ https://issues.apache.org/struts/browse/WW-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wes Wannemacher resolved WW-2265.
---------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.1.4)
                   Future

Although there are no Struts 2 commits for this, there is a JIRA at xwork and patch that when applied will resolve this issue - 
http://jira.opensymphony.com/browse/XW-609

> Modify MethodFilterInterceptor to support wildcard method names in the include/exclude lists
> --------------------------------------------------------------------------------------------
>
>                 Key: WW-2265
>                 URL: https://issues.apache.org/struts/browse/WW-2265
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Core Interceptors
>    Affects Versions: 2.0.9
>            Reporter: Scott Stanlick
>            Assignee: Wes Wannemacher
>             Fix For: Future
>
>
> I would like to propose a change to the MethodFilterInterceptorUtil class to allow support for wildcard method names on include/exclude list configurations.  The applyMethod behavior only supports specifically named methods or the "*" itself to indicate all/none.  In the spirit of design by convention, I am trying to develop an application that leverages symbolically constructed names and support for method names such as add* or remove* would provide benefits at the moment.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.