On 11/29/05, Niall Pemberton <[EMAIL PROTECTED]> 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 would say the merging of communities and effort is far and away the important part. that's certainly the interesting part to me. i can't imagine any sane way to do a code merger apart from the proposed compatibility layer. so the community/effort merging has been my understanding from the get-go. > > 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? > > > But again, that is my 2c which may not reflect the opinions of the > > Struts PMC as a whole. > > > > Don > > > > Niall Pemberton wrote: > > > On 11/29/05, Don Brown <[EMAIL PROTECTED]> wrote: > > > <snip> > > > > > >>>3) A users has invested his or her hard-earned cash in `WebWork' in > > >>>Action book. > > >>>Will contents of this tome still be relevant in Struts? > > >> > > >>Absolutely, since Struts Ti == WebWork 2.2, with some package name > > >>changes. > > >> > > > > > > </snip> > > > > > > <snip> > > > > > >>>5) What architectural components are going to be replaced in Struts ? > > >>>( And conversely in Webwork?) > > >> > > >>This is a tough question because we haven't started on the Struts > > >>compatibility layer so I can't tell you what we can support from Struts. > > >> WebWork will be imported as is, so I don't see anything replaced there > > >>initially, however, we might decide to remove some deprecations. > > >> > > >>I can tell you it is my personal goal for the Struts compatibility layer > > >>to support to some extent Struts Actions, ActionForms, Validator, and > > >>Tiles at least. > > > > > > </snip> > > > > > > I thought the proposal was to merge Struts and WebWork - from this and > > > what : Jason Carreira said on TSS the actual proposal is that Struts > > > Action/Classic is dumped and a migration path for Struts users to > > > WebWork 2.2 be provided? > > > > > > If this is the case then rather than calling this a proposed merger > > > wouldn't it be clearer to say that the proposal is to "deprecate > > > Struts in favour of WebWork"? > > > > > > Niall > > > > > > > > >>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]
