Doesn't a struts 2.x codebase need a roadmap first? Should there be some defined goals? Should it implement the same apis as struts 1.x so as to ease transition? Or should it be a whole new framework? Somehow I think the latter would be ill received.
On Thu, 2 Sep 2004 07:02:45 -0400, Ted Husted <[EMAIL PROTECTED]> wrote: > On Thu, 02 Sep 2004 11:43:37 +0200, Anders Steinlein wrote: > >ïJust want to throw in my voice here, as this is exactly what I've > >ïbeen thinking. I'm very pleased with Struts and use it on a daily > >ïbasis and I would love to contribute, but I don't really have the > >ïitches or time to fully read up on the current code. However, upon > >ïthe development of a "revolution"-Struts, I and surely many others > >ïwould be inspired to get involved right from the start. Just the > >ïthought of a Struts fully based on Servlet 2.4, JSP 2.0 and > >ïpossibly even J2SE 5.0 makes me all warm inside. ;) > > The best part is that we can have our cake and eat it too :) > > Those with itches for Servlet 2.4/JSP 2.0/J2SE 5.0 can begin work on Struts 2.x, > while others continue to maintain and enhance Struts 1.x. > > Many projects operate in a mode like this, including Apache HTTPD and Tomcat. > > We just need someone to step up and say, "OK, here's some starter code for Struts > 2.x, let's have at it." > > Meanwhile, those interested in the Struts 1.x base can maintain the status quo. > > -Ted. > > > > > --------------------------------------------------------------------- > 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]
