Struts 2 CRUD Example

-

This interceptor sets all parameters on the value stack.

This interceptor gets all parameters from {@link ActionContext#getParameters()} and sets them on the value stack by calling ValueStack#setValue(String, Object), typically resulting in the values submitted in a form request being applied to an action in the value stack. Note that the parameter map must contain a String key and often containers a String[] for the value.

The interceptor takes one parameter named 'ordered'. When set to true action properties are guaranteed to be set top-down which means that top action's properties are set first. Then it's subcomponents properties are set. The reason for this order is to enable a 'factory' pattern. For example, let's assume that one has an action that contains a property named modelClass that allows to choose what is the underlying implementation of model. By as suring that modelClass property is set before any model properties are set, it's possible to choose model implementation during action.setModelClass() call. Similarly it's possible to use action.setPrimaryKey() property set call to actually load the model class from persistent storage. Without any assumption on parameter order you have to use patterns like Preparable Interface.

Because parameter names are effectively OGNL statements, it is important that security be taken in to account. This interceptor will not apply any values in the parameters map if the expression contains an assignment (=), multiple expressions (,), or references any objects in the context (#). This is all done in the #acceptableName(String) method. In addition to this method, if the action being invoked implements the ParameterNameAware in terface, the action will be consulted to determine if the parameter should be set.
In addition to these restrictions, a flag ( ReflectionContextState#DENY_METHOD_EXECUTION ) is set such that no methods are allowed to be invoked. That means that any expression such as person.doSomething() or person.getName() will be explicitly forbidden. This is needed to make sure that your application is not exposed to attacks by malicious users.

While this interceptor is being invoked, a flag ( ReflectionContextState#CREATE_NULL_OBJECTS ) is turned on to ensure that any null reference is automatically created - if possible. See the type conversion documentation and the InstantiatingNullHandler javadocs for more information.

Finally, a third flag ( XWorkConverter#REPORT_CONVERSION_ERRORS ) is set that indicates any errors when converti ng the the values to their final data type (String[] -> int) an unrecoverable error occurred. With this flag set, the type conversion errors will be reported in the action context. See the type conversion documentation and the XWorkConverter javadocs for more information.

If you are looking for detailed logging information about your parameters, turn on DEBUG level logging for this interceptor. A detailed log of all the parameter keys and values will be reported.

Since XWork 2.0.2, this interceptor extends MethodFilterInterceptor, therefore being able to deal with excludeMethods / includeMethods p arameters. See Default Workflow Interceptor for

svn commit: r21481 - /dev/struts/2.3.34/

[struts] Git Push Summary

struts git commit: [maven-release-plugin] prepare release STRUTS_2_3_34

[06/14] struts-site git commit: Updates exported docs

[09/14] struts-site git commit: Updates exported docs

Getting Started

[03/14] struts-site git commit: Updates exported docs

Features

Usage

Features

Usage

[12/14] struts-site git commit: Updates exported docs

Struts 2 CRUD Example

Introduction

.war layout

Configuration files

WEB-INF/web.xml

[04/14] struts-site git commit: Updates exported docs

Understanding the Output

id="SiteGraphPlugin-Requirements">Requirements

Features

Usage

[14/14] struts-site git commit: Updates exported docs

[07/14] struts-site git commit: Updates exported docs