On 12/5/05, Don Brown <[EMAIL PROTECTED]> wrote: > My approach #2, to include 1.x jars and develop co-existing tools, lets > someone run a 1.x app "on" Struts Ti completely unchanged and with 100% > functionality, 1.x quirks and all. I think a user would mainly be > interested in that, and perhaps building new segments with Ti as the > opportunity arose.
In practice, I think your approach #2 and Laurie's #4 would end up being the same thing. I also think there are two ways for engineers like us to learn WebWork. One is by writing a bunch of WebWork applications, and two is by writing these type of migration tools. I don't see writing the migration tools as busy-work, and I see it as a way to develop a deep understanding of how Struts applications map to WebWork applications. The techniques we develop on the way to #2/#4 will serve us well as we try to migration 5-years of hard-won knowledge. My suggestion is that those with the itch pursue both frontiers: (A) Writing Struts applications the WebWork way, from the ground up, and (B) Porting Struts applications to WebWork via a migration layer IMHO, these approaches are complementary. In some cases, we will start with (B) and then move to (A) at our leisure. Of course, in a servlet environment, it's not an either/or proposition. I don't think Struts and Webwork services will collide, and we could have some request served by WebWork and other by Struts. A good group to ask about what migration strategies are most effective might be the WebWork users. I expect many of them have "been there and did that" already :) -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
