Page History

Sure, that's what the <include> element is for. Most xwork{{action.xml} files
already have one or more include elements:

<xwork>
    <include file="webworkaction-default.xml"/>
    <include file="config-browser.xml"/>
    <package name="default" extends="webworkaction-default">
....
    </package>
    <include file="other.xml"/>
</xwork>

This tells it The first include element tells the framework to load the webworkaction-default.xml from the webwork jar file
to get all of those , which it wil find in the struts-action.jar file. The action-default.xml file defines the "standard" interceptor and result definitions.

You can put your own <include> elements in your xwork action.xml interchangeably with
<package> elements. .. They configuration objects will be loaded in the same order as it reads
order of appearance. The framework reads the configuration from top to bottom and adds things as it reads themobjects as they are referenced.

@see com.opensymphony.xwork.config.ConfigurationManager
@see com.opensymphony.xwork.config.Configuration
@see com.opensymphony.xwork.config.impl.DefaultConfiguration
@see com.opensymphony.xwork.config.ConfigurationProvider
@see com.opensymphony.xwork.config.providers.XmlConfigurationProvider