for my current project, at a fairly low priority, i'd like to start migrating away from struts 1.1. i like webwork, and i am thinking that one strategy would be to gently migrate the app to webwork 2.2, with the idea that once struts 2 is production-ready i can (more?) easily migrate from webwork.
so is this a ridiculous idea? i really do see benefit taking positive steps away from struts (to webwork to struts 2), but not if those steps don't in some way follow the same path.
According to the Struts 2 home page we are promised a migration path from Struts 1 to Struts 2 when it officially arrives.
If you're not already familiar with WebWork, I'd certainly take the time to get more familiar with it and maybe write a few sample projects. To me it sounds like a waste of effort, though, to migrate a project to WebWork now, knowing you'll have to further migrate it to Struts 2 once it comes out.
If we get the Struts 1 to Struts 2 migration tool we are promised, you'll only have to migrate once instead of twice. [ August 23, 2006: Message edited by: Merrill Higginson ]