On 12/1/05, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > One other question - ti/phase2 is already there, and ti/phase1 comes > next? Are we counting down, whats the insight into the nomenclature?
Dessert first? :) When we started Struts Ti, it was conceived as a new framework that aimed to simplify the developers life requiring no configuration, supporting workflow through Beehive's page flow, and allowing developers to write code then refresh (with compiles automatically handled by the framework). It was decided this would be written on WebWork and so we proceeded. Just recently, we decided to merge with WebWork through Struts Ti. In an effort to a release of Struts Ti out ASAP, we decided to move the original lofty goals of Struts Ti to phase 2, with phase 1 being the WebWork merger. HTH, Don -Rahul > > > > I can tell you my approach I thought of today - replace the WebWork > > ServletDispatcher with a Common-Chain RequestProcessor then weave in a > > command or two that detects what type of action is being called, and > > delegates to the appropriate chain. I'm hoping to even use Struts > Action > > 1.3 as a dependency at first, so you have 100% Struts 1.x functionality, > yet > > you can start migrating sections to Struts Ti (WebWork) as you have > time. > > > > The Struts Ti repository is here: > > http://svn.apache.org/viewcvs.cgi/struts/sandbox/trunk/ti/ I'll be > adding a > > phase1 directory with the code. > > > > If you are interested in Struts Ti, I'd highly recommend pulling down > > WebWork and giving it a spin. You could also swing by your local > bookstore > > and thumb through the excellent WebWork in Action book from Manning :) > > > > Don > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
