I am all for simplifying the API to the end developer, but I wonder if those changes could be pushed to XWork in the form of an XWork 2.0, with, of course, the Web specific portions being added to SAF 2. I see the reasoning behind creating a layer to hide XWork (everything the user uses is Struts 2), but I believe the logical conclusion of that reasoning is to move XWork as well to Struts rather than adapter layer. I won't elaborate because I have in other threads. ;-)
----- Original Message ---- From: Don Brown <[EMAIL PROTECTED]> To: Struts Developers List <dev@struts.apache.org> Sent: Friday, May 5, 2006 4:36:13 PM Subject: Re: [action][Proposal] Architecture plan for Struts Action 2.0 Gabe wrote: > Where XWork is in this proposal is a little vague. Would this proposal break > the traditional division of roles between XWork and Webwork (Where SAF 2 is > where webwork was)? If so, how so? Is this proposing that there be an adapter > layer in SAF 2 to access XWork APIs? Would we be looking to push changes into > XWork? XWork would be hidden behind the new API for new projects, but available for older ones or just those that want to continue working with XWork directly. Again, it is too soon to expect fully-fleshed out details, but remember the end goal of simplifying the API to a end developer. That goal will drive any changes. Don > Thanks, > Gabe > > ----- Original Message ---- > From: Don Brown <[EMAIL PROTECTED]> > To: Struts Developers List <dev@struts.apache.org> > Sent: Friday, May 5, 2006 4:04:35 PM > Subject: [action][Proposal] Architecture plan for Struts Action 2.0 > > 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 > > --------------------------------------------------------------------- > 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] > > --------------------------------------------------------------------- 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]
