[
https://issues.apache.org/jira/browse/WW-4149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984502#comment-15984502
]
Hudson commented on WW-4149:
----------------------------
SUCCESS: Integrated in Jenkins build Struts-JDK7-master #624 (See
[https://builds.apache.org/job/Struts-JDK7-master/624/])
WW-4149 Introduces an empty stack (lukaszlenart: rev
8f75e1a19dfde5b55bb3265737d81c8bfa8ccb39)
* (edit) core/src/main/resources/struts-default.xml
* (add) core/src/main/java/org/apache/struts2/interceptor/NoOpInterceptor.java
> 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)
