Page History

The migration strategy of Struts Action 1 developers moving to Struts Action 2 involves four non-exclusive paths:

1. Run the Struts Action 1 SAF1 application as is - Action 2 SAF2 will ship with the Action 1.3 jars to allow users to run JARs, so existing applications can run unchanged. This is particularly important where frameworks have to be "approved" and by shipping with Action 1.x jars, we help shops make a clean upgradeTeams can upgrade to the "latest" version without changing a thing.
2. Dual processor, shared resources - Action 1.x and Action 2.0 servlets running SAF1 and SAF2 can run side by side, however, certain resources like message resourceswithin the same web application. Teams can implement new features in the latest version, and migrate older pieces as needed. Optionally, some common resources may be shared between SAF1 and SAF2, like messages, validation rules, and tiles configuration should be able to be shared without conflicts. This allows the user to migrate pieces of their application at a time without having to replicate everything in the new environment.Tiles configurations, making for an even smoother migration.
3. Use a conversion wizard - It might may be possible to create a tool that reads the web.xml and struts SAF1 configuration files, and generates the necessary Action 2 configuration files. Actions, ActionForms, and even PlugIns could be ran as is on the new Action 2 framework. This path also serves as a training tool to assist the user in understanding how Action 2 workscorresponding SAF2 classes, pages, and configuration files. While 100% compatibility is probably impossibleunlikely, we could make a strong effort to migrate convert the application, marking areas that don't migrate correctlyneed attention. Comparing the converted files with the originals could also serve as a training tool.
4. Study known Action 1 SAF1 applications, rewritten in for Action 2 - Action 2 will ship with familiar SAF2 - Familiar applications such as the Struts Mailreader are being rewritten to be built on Action 2. This demonstration will aid full conversion efforts by demonstrating best practices in the new frameworkdemonstrate best practices for SAF2.

Next: Migration Tools

...

This page originally adopted from http://wiki.apache.org/struts/MigrationStrategy.