WebWork Merger FAQ
Benefits of handling the merger as an Apache project include:
Probably not. Apache Struts already uses other products internally, and we can use SiteMesh and XWork too.
Not yet. If we are able to create a clear and simple migration path from Struts 1.x to Struts Ti, then the Struts PMC may want to consider calling the product Struts Action Framework 2.x, but it's too soon to say.
Yes, we expect that it will. The Struts and WebWork committers are also Struts and WebWork users, and we would want to keep both products up to date. It's also possible that we may help people using the frameworks migrate to Ti step-by-step through a series of changes to the existing codebases.
Yes, using migration tools and compatibility classes, we hope to run most existing applications out of the box and provide a clear migration path that existing applications can follow.
For the first phase, yes. The first phase of Ti is expected to be WebWork 2.2. with a Struts 1.x migration layer. In the second phase of Ti, there would be additional changes, just as there might have been for WebWork 3.x.
If successful, Struts Ti would become Struts Action 2.x, and it likely that most Struts 1.x references would not be relevent. Of course, this is often the case when a product rolls the major version number.
We expect that key Struts 1.3 technologies and all WebWork 2.2 technologies will be supported.
Our primary target is Struts 1.3 and WebWork 2.2, but we'd like to support great ideas from other frameworks too.