Sean Gilligan wrote:
I'm just asking about options that might make it easier to change directions in the future. I like the way the SpringMVC people try to give you a migration path from other frameworks. (I'm looking at using that technique with some Jakarta Turbine Screens and Actions, but haven't gotten there yet.)
Migration is something that WebWork never took too seriously, and that will definitely change in Struts Action 2. We are trying to combine the next generation feature you'd expect with a smooth migration path for existing Struts and WebWork users (and possibly Spring MVC, actually). We had initially tried to work with Spring MVC through the "Clarity" initiative, but that didn't go anywhere unfortunately.
Don
-- Sean
