RE: [Webwork-devel] [Fwd: WebWork - OpenSymphony]

[<fbe...@py...>]

It is true that there is an emphasis on JSPs but for example, the caching
engine in OSCache is generic enough so that it is possible to use it with
other things than JSP.
There has always been an effort to keep the modules dependant on as less
things as possible.

I want to emphasize on the fact that the proposition involves promoting the
modules together and also may be have subprojects to glue things together. I
think that if the code of all modules is well done it would be possible to
have different distributions through ant targets depending on what you want
to use.
This would put the emphasis on developing highly modularizable components.

I don't see any merge in code.
But collaborations (synergy) in developing and promoting J2EE components and
tools.
WebWork contributors have done some great work and will continue to do so
with the same independance.
Open Symphony can bring new ideas in the process and vice-versa.

That is Open Source at its best !!

Cheers
______________________________________________
François Beauregard
Pyxis Technologies
Vice-président, recherche et développement

Tel: (450) 681-9094
Fax: (450) 681-5758
fbe...@py... <mailto:fbe...@py...>



-----Original Message-----
From: web...@li...
[mailto:web...@li...]On Behalf Of Dave
Bryson
Sent: February 11, 2002 10:34 AM
To: Rickard; web...@li...
Subject: Re: [Webwork-devel] [Fwd: WebWork - OpenSymphony]


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