struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jasper Rosenberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (WW-4149) No easy way to have an empty interceptor stack if have default stack
Date Mon, 17 Mar 2014 12:45:43 GMT

    [ https://issues.apache.org/jira/browse/WW-4149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937754#comment-13937754
] 

Jasper Rosenberg commented on WW-4149:
--------------------------------------

I actually use an empty stack a ton.  Pretty much anytime we have a view that doesn't look
at query parameters (but is still dynamic because the user may be logged in, etc), I use an
empty stack since it is just overhead at that point.

> 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
>             Fix For: 2.3.x
>
>
> 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.2#6252)

Mime
View raw message