Page History

...

1. I chose the version 2.5 because it indicates that Struts 2 applications will continue to work, however, the jump in the minor version indicates significant functionality for those that want to take advantage of it.
2. My main pain point here is the difficult upgrade process for Struts applications. It should be possible to deploy an application, written against an older version of Struts, on the latest version of the framework. Only OSGi, with its proper version support, can handle running multiple versions of the same interface in the same JVM.
3. To elaborate on the last point, I want to ensure Struts 2 is a viable and attractive framework for not just the 6-month project, but the 10 year project as well. In order to be the 10-year app framework of choice, we have to have a way to allow new application features to be written on the latest and greatest Struts framework without requiring rewrites of 5-year-old code. By encouraging applications to be written into discrete bundles, the large, complex app can be broken into functional pieces with their own dependencies and needs. Applications for years have been using the multi-jar approach to complexity, but OSGi takes it to the next level.

References

• OSGi and Modularity blog post
• OSGi appliance
• Apache Felix
• Spring Dynamic Modules
• Excellent OSGi tutorial