Struts 2 configuration

Struts 2 Configuration

In this section we will discusses the basic configuration required for a Struts 2 application. Here we will see what will be configured in few important configuration files : web.xml, struts.xml, struts-config.xml and

The web.xml file:

The web.xml configuration file is a J2EE configuration file that determines how elements of the HTTP request are processed by the servlet container over the server. It is not strictly a Struts2 configuration file, but it is a file that needs to be configured for Struts2 to work smothely and properley. This file provides an entry point for any web application. The entry point of Struts2 application will be a filter defined in deployment descriptor (web.xml). Hence we will define an entry of FilterDispatcher class in web.xml. The web.xml file needs to be created under the folder WebContent/WEB-INF folder in the project.

<?xml version="1.0" encoding="UTF-8"?>

<web-app xmlns:xsi="" xmlns="" xmlns:web="" xsi:schemaLocation="" id="WebApp_ID" version="3.0">
















Note that we map the Struts 2 filter to /*, and not to /*.action which means that all urls will be parsed by the struts filter.

The struts.xml file:

The struts.xml file contains the configuration information that you will be modifying as actions are developed. This file can be used to override default settings for an application, for example struts.devMode = false and other settings which are defined in property file. This file can be created under the folder WEB-INF/classes.

<?xml version="1.0" encoding="UTF-8" ?>

<!DOCTYPE struts PUBLIC "-//Apache Software Foundation//DTD Struts

Configuration 2.1//EN" "">


<package name="default" extends="struts-default">

<action name="HelloWorld" class="">

<result name="SUCCESS">/success.jsp</result>

<result name="FAILURE">/index.jsp</result>

<result name="input">index.jsp</result>




The first thing to note is the DOCTYPE. All struts configuration file need to have the correct doctype as shown in our little example. <struts> is the root tag element, under which we declare different packages using <package> tags. Here <package> allows separation and modularization of the configuration. This is very useful when you have a large project and project is divided into different modules.

Suppose our project has three domains - business_applicaiton, customer_application and staff_application, you could create three packages and store associated actions in the appropriate package. The package tag has the following attributes:

Attribute Description

name (required) The unique identifier for the package

extends Which package does this package extend from? By default, we se struts-default as the base package.

abstract If marked true, the package is not available for end user consumption.

namesapce Unique namespace for the actions.

The constant tag along with name and value attributes will be used to override any of the following properties defined in, like we just set struts.devMode property. Setting struts.devMode property allows us to see more debug messages in the log file.

We define action tags corresponds to every URL we want to access and we define a class with execute() method which will be accessed whenever we will access corresponding URL.

Results determine what gets returned to the browser after an action is executed. The string returned from the action should be the name of a result. Results are configured per-action as above, or as a "global" result, available to every action in a package. Results have optional name and type attributes. The default name value is "success".

Struts.xml file can grow big over time and so breaking it by packages is one way of modularizing it, but struts offers another way to modularize the struts.xml file. You could split the file into multiple xml files and import them in the following fashion.

<?xml version="1.0" encoding="UTF-8"?>


"-//Apache Software Foundation//DTD Struts Configuration 2.0//EN"



<include file="my-struts1.xml"/>

<include file="my-struts2.xml"/>


The other configuration file that we haven't covered is the struts-default.xml. This file contains the standard configuration settings for Struts and you would not have to touch these settings for 99.99% of your projects. For this reason, we are not going into too much detail on this file. If you are interested, take a look into the at the file available in struts2-core-2.2.3.jar file.

SN             Interceptor & Description

1             struts-config            This is the root node of the configuration file.

2             form-beans             This is where you map your ActionForm subclass to a name. You use this name as an alias for your ActionForm throughout the rest of the struts-config.xml file, and even on your JSP pages.

3             global forwards       This section maps a page on your webapp to a name. You can use this name to refer to the actual page. This avoids hardcoding URLs on your web pages.

4             action-mappings      This is where you declare form handlers and they are also known as action mappings.

5             controller                 This section configures Struts internals and rarely used in practical situations.

6             plug-in                    This section tells Struts where to find your properties files, which contain prompts and error messages

For more detail on struts-config.xml file, kindly check your struts documentation.

The file.

This configuration file provides a mechanism to change the default behavior of the framework. Actually all of the properties contained within the configuration file can also be configured in the web.xml using the init-param, as well using the constant tag in the struts.xml configuration file. But if you like to keep the things separate and more struts specific then you can create this file under the folder WEB-INF/classes.

The values configured in this file will override the default values configured in which is contained in the struts2-core-x.y.z.jar distribution. There are a couple of properties that you might consider changing using file:

When set to true, Struts will act much more friendly for developers

struts.devMode = true

Enables reloading of internationalization files

struts.i18n.reload = true

Enables reloading of XML configuration files

struts.configuration.xml.reload = true

Sets the port that the server is run on

struts.url.http.port = 8080

Here any line starting with hash (#) will be assumed as a comment and it will be ignored by Struts 2.