I'm trying to override one of three interceptor parameters in an action
specific config using method #2 described in
http://struts.apache.org/2.0.11.1/docs/interceptors.html#Interceptors-InterceptorParameterOverriding.
Unfortunately the other two parameters that I'm not overriding are not being
taken from the default stack definition and are ending up as null on the
interceptor. Before I open a Jira bug (or enhancement request), I thought I'd
make sure a) this isn't user error b) the expected behavior is "my" expected
behavior (i.e. bug vs. enhancement). Below is a sample action config showing
what I'm attempting...
<package name="packageA"...>
<interceptors>
<interceptor name="myInterceptor" class="..."/>
<interceptor-stack name="myStack">
<interceptor-ref name="defaultStack"/>
<interceptor-ref name="myInterceptor">
<param name="paramA">defaultValueA</param>
<param name="paramB">defaultValueB</param>
<param name="paramC">defaultValueC</param>
</interceptor-ref>
</interceptor-stack>
</package>
With the following action config, the "myInterceptor" interceptor's paramA &
paramB are null and not "defaultValueA" and "defaultValueB" as expected/desired.
<package name="packageB" extends="packageA"...>
<action name="myAction" class="myActionClass">
<interceptor-ref name="myStack">
<param name="myInterceptor.paramC">actionSpecificValue</param>
</interceptor-ref>
</action>
</package>
Thanks,
Jon