Re: Re: [Webwork-devel] Branch or Commit , which?
Brought to you by:
baldree,
rickardoberg
From: matt b. <mat...@ho...> - 2002-02-04 20:24:36
|
>From: Jim...@do... >To: "matt baldree" <mat...@ho...> >Subject: Re: Re: [Webwork-devel] Branch or Commit , which? >Date: Mon, 4 Feb 2002 12:40:59 -0500 > >I would recommend that WebWork core be defined as all classes that are >invoked prior to the RequestDispatcher.forward() call. This would mean >that the Velocity servlet dispatcher and the webwork taglibs are >distributed as an add-on to the core. > >I have another post lurking somewhere why I feel this is a good decision. >Bottom line is, I feel WebWork should be view agnostic, as do most of us. I agree overall, but I think the best approach for Feb. 15 is just core and examples. Later core could be split further. >Since some (many?) WebWork projects do not rely on JSP, thus no taglibs, >why tie the development and release of the Action engine (the real core) >to the release schedule of the JSP taglibs? The real core of WebWork could >have gone 1.0 about 6 months ago. Actually, we have been waiting on the docs and nothing more. > >$.02, >-jim _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp. |