Re: Migration Path

are working on > getting a release out that is pretty much a renamed WebWork 2 with a > few minor improvements, but if you are on the dev list, you'll see > there is a lot more discussion on more radical changes possibly after > that. > > The bottom line is it is a primary

Re: Migration Path

on on more radical changes possibly after that. The bottom line is it is a primary goal of Struts Action 2 to have an easy migration path from Struts Action 1 and WebWork 2, so no matter how Struts Action 2 changes in the future, we plan to minimize, if not eliminate, the amount of changes you'll h

Re: Migration Path

more discussion on more radical changes possibly after that. The bottom line is it is a primary goal of Struts Action 2 to have an easy migration path from Struts Action 1 and WebWork 2, so no matter how Struts Action 2 changes in the future, we plan to minimize, if not eliminate, the amount of changes y

Migration Path

Hello, Since it seems pretty much settled that SAF2 == WW2 with different package names. I'm ready to get my head wet now with WW. I know the transition will be easier if I wait ... yadda yadda. I was told that one could actually start using WW inside my existing struts projects and incrementally