Just as some people continue to use WebWork 1.xx (JIRA) I imagine people will continue to use SAF1 regardless of how easy the migration path is.
I always assume it would take a day or two to convert existing WW code to SAF2 so at the end of the day just picking a direction is progress. :) Cheers, Eric On 5/5/06, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
On 5/5/06, Don Brown <[EMAIL PROTECTED]> wrote: > Ok, let's just make this an official proposal and focus all of this discussion: > > I propose that the architecture plan for Struts Action 2.0 includes the following: > > 1. A re-design of the API to simplify the framework the users see > 2. Backwards-compatibility support for WebWork 2 and Struts 1.x applications > 3. Continue to use XWork for a) compatibility reasons and b) the core > implementation of the new API > 4. A target GA release by August > > This means for current WebWork 2 users: > 1. WebWork continues to apply bug fixes for the WebWork 2.1.x and 2.2.x branches > 2. Migration to Struts Action 2.0 should take hours, not days, weeks, but > probably not minutes. > > For Struts Action 1 users: > 1. Struts Action 1.x will continue to be developed actively > 2. Migration to Struts Action 2.0 should take days, using available migration > tools and compatibility libraries > > I think this proposal is a good middle ground between folks that want WebWork > 2.2 with just package renaming, and others that want a completely new framework. > > Please register your comments and if necessary, I'll call a vote so we can > decide this once and for all, and get back to coding. > > Don SAF1 could have future if migration to SAF2 were impossible or too complicated. But according to your plan, migration from SAF1 to SAF2 should take days. What is the point of keeping Action 1.x "to be developed actively"? I am not objecting, I am just asking. Trying to understand where I am ;-) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
