You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

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

  1. Run the SAF1 application as is - SAF2 will ship with the Action 1.3 JARs, so existing applications can run unchanged. Teams can upgrade to the "latest" version without changing a thing.
  2. Dual processor, shared resources - SAF1 and SAF2 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 SAF1 and SAF2, like messages, validation rules, and Tiles configurations, making for an even smoother migration.
  3. Use a conversion wizard - It may be possible to create a tool that reads the web.xml and SAF1 configuration files, and generates the corresponding SAF2 classes, pages, and configuration files. While 100% compatibility is unlikely, we could make a strong effort to convert the application, marking areas that need attention. Comparing the converted files with the originals could also serve as a training tool.
  4. Study known SAF1 applications, rewritten for SAF2 - Familiar applications such as the Struts Mailreader are being rewritten to demonstrate best practices for SAF2.

Next: Migration Tools

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

  • No labels