An interceptor that copies all the properties of every object in the value stack to the currently executing object, except for any object that implements Unchainable. A collection of optional includes and excludes may be provided to control how and which parameters are copied. Only includes or excludes may be specified. Specifying both results in undefined behavior. See the JavaDocs for [ReflectionProvider#copy(Object, Object, java.util.Map, java.util.Collection, java.util.Collection)](/maven/struts2-core/apidocs/org/apache/struts2/util/reflection/ReflectionProvider.html#copy(java.lang.Object, java.lang.Object, java.util.Map, java.util.Collection, java.util.Collection)) for more information.
It is important to remember that this interceptor does nothing if there are no objects already on the stack. This means two things:
- you can safely apply it to all your actions without any worry of adverse affects.
- it is up to you to ensure an object exists in the stack prior to invoking this action. The most typical way this is done is through the use of the chain result type, which combines with this interceptor to make up the action chaining feature.
By default Errors, Field errors and Message aren't copied during chaining, to change the behaviour you can specify the below three constants in struts.properties or struts.xml:
struts.xwork.chaining.copyErrors - set to true to copy Action Errorsstruts.xwork.chaining.copyFieldErrors - set to true to copy Field Errorsstruts.xwork.chaining.copyMessages - set to true to copy Action Messages<constant name="struts.xwork.chaining.copyErrors" value="true"/>
By default the Chaining Interceptor copies all properties of the objects on the value stack into the target action, regardless of any @StrutsParameter annotation. To restrict copying to annotated properties only, set the global constant:
<constant name="struts.chaining.requireAnnotations" value="true"/>
When enabled (default is false):
@StrutsParameter are copied; rejected properties are skipped and logged at WARN.ParameterAuthorizer service as the Parameters Interceptor, keeping semantics consistent.Action chaining makes the data path into the target action implicit: the target is populated from whatever happens to be on the value stack rather than from an explicit call. Keep that in mind when designing chained actions:
includes or excludes parameters to limit the copied properties to the ones the target genuinely needs.See also Where authorization applies for an overview of the channels that can populate an action.
excludes (optional) - the list of parameter names to exclude from copying (all others will be included)includes (optional) - the list of parameter names to include when copying (all others will be excluded)There are no known extension points to this interceptor.
Simple example how to chain two actions
<action name="someAction" class="com.examples.SomeAction"> <interceptor-ref name="basicStack"/> <result name="success" type="chain">otherAction</result> </action> <action name="otherAction" class="com.examples.OtherAction"> <interceptor-ref name="chain"/> <interceptor-ref name="basicStack"/> <result name="success">good_result.ftl</result> </action>
This examples chains two actions but only one property from first action is copied to another
<action name="someAction" class="com.examples.SomeAction"> <interceptor-ref name="basicStack"/> <result name="success" type="chain">otherAction</result> </action> <action name="otherAction" class="com.examples.OtherAction"> <interceptor-ref name="chainStack"> <param name="chain.includes">prop1</param> </interceptor-ref> <result name="success">good_result.ftl</result> </action>