You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Lukasz Lenart (JIRA)" <ji...@apache.org> on 2017/04/26 06:23:04 UTC

[jira] [Resolved] (WW-4149) No easy way to have an empty interceptor stack if have default stack

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

Lukasz Lenart resolved WW-4149.
-------------------------------
    Resolution: Fixed
      Assignee: Lukasz Lenart

Introduced an empty stack using the {{NoOpInterceptor}} https://cwiki.apache.org/confluence/display/WW/NoOp+Interceptor

> No easy way to have an empty interceptor stack if have default stack
> --------------------------------------------------------------------
>
>                 Key: WW-4149
>                 URL: https://issues.apache.org/jira/browse/WW-4149
>             Project: Struts 2
>          Issue Type: Improvement
>          Components: Core Interceptors
>    Affects Versions: 2.3.15.1
>            Reporter: Jasper Rosenberg
>            Assignee: Lukasz Lenart
>             Fix For: 2.5.next
>
>
> If you have an action that you don't want to have any interceptors, if there is a defaultStack defined, you can't.
> My work around was to create an NoOpInterceptor that did nothing, and then declare interceptor stack that just included it to use.
> It used to be that you couldn't include an empty interceptor stack at all.  That seems to not blow up now, but unfortunately it appears that it is treated as if it doesn't exist, and the defaultStack is used instead.
> I think a declared interceptor stack on an action should override the default, even if it is empty.
> Could then also provide an "emptyStack" interceptor in struts-default.xml that people could use when they wanted this behavior.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)