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]
