Page History

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

1. Run Dual processor, shared resources - Add the Struts Action 1.x as is - Action 2.0 will ship with the Action JARs to your exisitng Struts 1.3 jars to allow users to run existing applications 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 upgrade.Dual processor, shared resources - Action 1.x and Action 2.0 servlets running side by side, however, certain resources like message resources, 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 environmentapplication. Configure S2 to handle *.action requests s and let S1 handle *.do requests. S1 and S2 can run side by side, within 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 S1 and S2, like messages, validation rules, and Tiles configurations, making for an even smoother migration.
2. Study known Struts 1 applications, rewritten for Struts 2 - Familiar applications such as the Struts Mailreader are being rewritten to demonstrate best practices for Struts 2.
3. Use a conversion wizard - It might may be possible to create a tool that reads the web.xml and struts S1 configuration files, and generates the necessary Action 2.0 configuration files. Actions, !ActionForms, and even !PlugIns could be ran as is on the new Action 2.0 framework. This path also serves as a training tool to assist the user in understanding how Action 2.0 works. corresponding S2 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 correctly.Study known Action 1.x applications, rewritten in for Action 2.0 - Action 2.0 will ship with familiar applications such as the Struts Mailreader rewritten to be built on Action 2.0. This demonstration will aid full conversion efforts by demonstrating best practices in the new framework.need attention. Comparing the converted files with the originals could also serve as a training tool.

Next: Migration Tools

...

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