THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Two key configuration files utilized From a Struts developer point of view, the one required configuration file used by the framework are is web.xml and struts.xml. The configuration elements in these two files will reference any other required or optional configuration files. From here, you have full control over how Struts configures both itself and your application. By default, Struts will load a set of internal configuration files to configure itself, then another set to configure your application, however it is possible to build an entire Struts application without writing a single configuration file other than web.xml.
The table lists the files that you can use to configure the framework for your application. Some configuration files can be reloaded dynamically. Dynamic reloading makes interactive development possible. See Reloading configuration for more.
File | Optional | Location (relative to webapp) | Purpose |
|---|---|---|---|
no | /WEB-INF/ | Web deployment descriptor to include all necessary framework components | |
no yes | /WEB-INF/classes/ | Main configuration, contains result/view types, action mappings, interceptors, and so forth | |
yes | /WEB-INF/classes/ | Framework properties | |
yes | /WEB-INF/lib/struts2-core.jar | Default configuration that should be included in | |
yes | /WEB-INF/classes/ | Default macros referenced by | |
struts-plugin.xml | yes | At the root of a plugin JAR | Optional configuration files for Plugins in the same format as |
yes | /WEB-INF/classes/ | Override the default Velocity configuration |
...
By default, the following packages are searched:
- org.apache.struts2.static
- template
Additional packages can be specified by providing a comma separated list to the configuration parameter named "packages" (configured in web.xml for the FilterDispatcher filter). When specifying additional static content, you should be careful not to expose sensitive configuration information (such as the password to a database).