Niall Pemberton wrote:
On 11/29/05, Don Brown <[EMAIL PROTECTED]> wrote:
First, we bring in the WebWork 2.2 code which forms the Struts Ti core.
Then, we develop a Struts compatibility layer. Along the way, if we
see anything from Struts Action 1.x that should also go into Struts Ti
core, we can add it. Honestly, I don't really see anything of Struts
Action 1.x that isn't done better in WebWork, so yes, I still think it
is a merger, but being this is targetted for Struts Action 2.0, I think
it is appropriate to be such a large rewrite. Even if we wrote Struts
Action 2.0 from scratch, I doubt we'd see much from Struts Action 1.x
we'd want to carry over.
Its probably a great plan to switch to WebWork 2.2 but I still don't
see how you can say its a "merger" if no Struts code is involved -
merger in terms of community, but not software.
I view this merger as first, one of projects/community, and second, one of code.
Just because the Struts Action 1.x compatibility layer will be separate from
the Struts Ti core (WebWork 2.2), doesn't mean we haven't merged code. In fact,
I'd consider that a prime example of the merger, because the Struts Action code
will need to be "merged" into the Struts Ti core framework while retaining much
of its original functionality.
And as with WebWork 1.x and as we've been saying from the beginning,
Struts Action 1.x will continue to be developed and supported, so I
wouldn't even call that a deprecation.
If its agreed we move to WebWork 2.2 for Struts 2.0 then why would we
continue developing Struts 1.x? I wouldn't want to, it would be a
waste of time - would you anticipate doing any/much Struts 1.x
development in this scenario?
As for continuing to develop Struts Action 1.x, I imagine not everyone will move
to Struts Action 2.0, particularly, if they have legacy applications. I'd even
guess we'd have committers who still want to work with 1.x, just as Shale didn't
automatically suck up all the Struts Action 1.x development work. I know as I
go back to add features to my legacy Struts applications, I might want to add a
feature or two that I've enjoyed from Struts Action 2.0.
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
