Re: [Webwork-devel] [Fwd: WebWork - OpenSymphony]
Brought to you by:
baldree,
rickardoberg
From: Victor S. <vsa...@ho...> - 2002-02-11 18:10:54
|
Hi Dave: I have written the following items for Velocity/WebWork: 1. Sitemesh #decorate directive. 2. OScache #cache directive 3. Made a better Webwork/Velocity Servlet just for your information :) ... it wouldn't be a kill as I don't use JSP anymore, but JSP is useful to a lot of people... WebWork is agnostic and a lot of OpenSymphony too... It's been designed like that. Cheers, /V >From: Dave Bryson <db...@in...> >To: Rickard <ri...@mi...>, >"web...@li..." <web...@li...> >Subject: Re: [Webwork-devel] [Fwd: WebWork - OpenSymphony] >Date: Mon, 11 Feb 2002 09:33:45 -0600 > >On Monday 11 February 2002 08:25 am, you wrote: > > I just got this from OpenSymphony. It's an interesting proposal, but I'd > > like to hear your input whether you think it's good or not. What are the > > pro's and con's? > >It seems like some of the key components of OpenSymphony ( OSCache and >Sitemesh ) are slanted towards JSP. Can these components be used with >Velocity or would the merge kill Velocity support? > >One of the main reasons I moved to WebWork was it's simplicity and >few dependencies on external libraries. I fear a merge would evolve >towards >bloat - causing an eventual dependency creep between OpenSymphony and >WebWork. > >IMO, WebWork is best served by itself. > >dave >-- >Dave Bryson > >_______________________________________________ >Webwork-devel mailing list >Web...@li... >https://lists.sourceforge.net/lists/listinfo/webwork-devel _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com |