Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Main Configuration Files

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 action.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 Below are all the files that you may need to be aware of. Some of this configuration files can be reloaded dynamically, making development much easier. Dynamic reloading makes interactive development possible. See Reloading configuration for more information.

File

Optional

Location (relative to webapp)

Purpose

web.xml

no

/WEB-INF/

Web deployment descriptor to include all necessary framework components

actionstruts.xml

no yes

/WEB-INF/classes/

Main configuration, contains result/view types, action mappings, interceptors, and so forth

actionstruts.properties

yes

/WEB-INF/classes/

Framework properties

actionstruts-default.xml

yes

/WEB-INF/lib/struts-action-x.x.jar struts2-core.jar

Default configuration provided by Struts

struts-default.vm

yes

/WEB-INF/classes/

Default macros referenced by velocity.properties

struts-plugin.xml

yes

At the root of a plugin JAR

Optional configuration files for Plugins in the same format as struts.xml. Default configuration that should be included in action.xml

velocity.properties

yes

/WEB-INF/classes/

Override the default velocity 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 "/actionstruts/" denotes that static content is required, and then mapping the value after "/actionstruts/" to common packages in Struts Action 2 the framework and, optionally in the applciationapplication's class path.

By default, the following packages are searched:

  • org.apache.

...

  • struts2.static
  • template

Additional packages can be specified by providing a comma seperated 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 (i.e. database password).such as the password to a database).

Next: Application Servers