THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Main Configuration Files
Two key configuration files utilized by the framework are web.xml and action.xml. The configuration elements in these two files will reference any other required or optional configuration files.
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 |
/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/struts-action-x.x.jar |
Default configuration that should be included in |
|
yes |
/WEB-INF/classes/ |
Override the default velocity configuration |
Static Content
Common static content that is needed by the framework (JavaScript and CSS files, etc.) is served automatically by the FilterDispatcher filter. Any request starting with "/action/" denotes that static content is required, and then mapping the value after "/action/" to common packages in Struts Action 2 and, optionally in the applciation's class path.
By default, the following packages are searched:
- org.apache.struts.action2.static
- template
Additional packages can be specified by providing a comma seperated 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 (i.e. database password).