I am a struts user who has recently began programming in webwork, to get
a head start for action 2.  Having just spent many hours researching,
reading about and experimenting with webwork, I personally hope that you
start with a version of action 2 that resembles webwork pretty closely.
I wonder how many other people are in my shoes. If ease of migration is
a major concern for the project, maybe a survey on struts-user would be
useful, something like:

Regarding Struts Action 2 and Webwork do you...
[ ] plan to keep using struts action 1 for new apps
[ ] plan to use struts 2 for new apps when released
[ ] plan to use webwork for new apps til struts 2 is released 

I think that having the current webwork user base as a resource that may
help the much larger struts users base to migrate is a consideration
that should be taken in your deliberations as well, because if struts
action 2 is new everyone, that may make adoption slower.

Dave

On Fri, 2006-05-05 at 13:04 -0700, Don Brown 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
> 
> ---------------------------------------------------------------------
> 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]

Reply via email to