Home > Guides > Migration Guide > Key Changes From WebWork 2 |

Apache Struts 2 Documentation
Key Changes From WebWork 2
Edit Page Browse Space Add Page Add News

The upgrade path from WebWork 2 to Struts 2 is smooth glide. Here's the roadmap.

### System Platform

- Struts 2 is dependant on XWork 2 (beta-1).
- Java 1.5 is required to build Struts 2.
  - For Java 1.4 deployments, RetroTranslater JARS are available with the distribution.

For other changes from WebWork 2, see the "Members to rename", "New property settings", "New features or feature changes", and "Removed or deprecated" sections.

#### Members to rename

WebWork 2 | Struts 2
--- | ---
`com.opensymphony.xwork.*` | `com.opensymphony.xwork2.*`
`com.opensymphony.webwork.*` | `org.apache.struts2.*`
`xwork.xml` | `struts.xml`
`webwork.properties` | `struts.properties`
DispatcherUtil | Dispatcher
com.opensymphony.webwork.config.Configuration | org.apache.struts2.config.Settings

The tag prefix conventions in the example applications have changed.

JSP | s: | <s:form ...>
Freemarker | s. | <@s.form ...>
Velocity | s | #sform ( ... )

#### New property settings

struts.enable.DynamicMethodInvocation | Enable support for the hardwired `action!alias` syntax (Default is `TRUE`)

Icon

It is recommended that all applications specify the DynamicMethodInvocation setting for now, since the default may change. The recommended approach to action aliasing is to use wildcard aliases instead of the hardwired bang.

#### New features and feature changes

- Various changes to ConfigurationManager
  - ConfigurationManager is no longer a static factory. It is now an instance created through Dispatcher. Custom configuration could be done through DispatcherListener.
  - Custom configuration to ConfigurationManager and Configuration cannot be done statically anymore, instead use Dispatcher's DispatcherListener to achieve the same effect.
- The `prepare` interceptor now uses reflection to call prepare_Method_ where method is the action method configured for the particular action in `struts.xml`.
- DefaultWorkflowInterceptor (named `workflow` in `struts-default.xml`) now uses reflection to call `validateMethod` on the action class that implements Validateable interface where `method` is the action method configured for the particular action in `struts.xml`.
- The tooltip library used by the xhtml theme was replaced by Dojo's tooltip component.
- Datepicker tag has been renamed to datetimepicker and is now using dojo (limited in terms functionality and internationalization)
- Tiles integration plugin is available.
- Wildcards can be specified in action mappings.
- MessageStoreInterceptor is introduced to allow field errors / action errors and messages to be store and retrieve through session, resulting them to be preservable across request.

#### Removed or deprecated

AroundInterceptor | The AroundInterceptor has been removed. If your application extends the AroundInterceptor, either import the class into your source code form WebWork 2 (pursuant to the Open Symphony License) and modify it to server as your own base class, or rewrite your interceptor.
`oldSyntax` | Support for the "oldSyntax" is removed.
Rich text editor tag | Rich text editor tag is removed and replaced by Dojo's rich text editor
`doActionMethod` | The convention of trying a "do" form of an action method is not supported. In WebWork, try to execute `submit` method in the action, fail try to execute `doSubmit` method in the action if Step 1, fail fail In Struts, try to execute `submit` method in the action, fail fail
`default method` | Calling the "default" method via "doDefault" is not supported.
IOC framework | Deprecated in WebWork 2.2, the internal IOC framework is removed in Struts 2. Spring is the ObjectFactory default.