Re: [Webwork-devel] [Fwd: WebWork - OpenSymphony]
Brought to you by:
baldree,
rickardoberg
From: Toby H. <tob...@ho...> - 2002-02-11 23:53:38
|
OK, This is probably out of line, as I am just a lurker and user of webwork, but I would have similar concerns...small groups achieve more faster, and if you look at WW as providing a core service with value-added features then there is not that compelling an argument to 'merge'...the major issue i would see is loss of control. from my point of view (as a fairly new convert), WW is good because it is small, cohesive and relatively easy to learn...the core package is elegant and the value-added features are good for particular re That said, closer ties are always a good thing, however, and there are features of OS that are definitely worth integrating with WW. Close relationships will help get these features sooner and assist in adapting to changes in either codebase as they evolve. cheers, toby >From: Jim...@do... >To: webwork-devel <web...@li...> >Subject: Re: [Webwork-devel] [Fwd: WebWork - OpenSymphony] >Date: Mon, 11 Feb 2002 16:01:59 -0500 > >I feel that WebWork is synergistic with many technologies, such as >Velocity, OSCache, JSP, etc. > >I also tend to think of "core" WebWork consisting of the ServletDispatcher >and patterns built upon the ActionFactory. The JSP tag libraries to me are >a secondary "value-added" technology that is not intregral to WebWork. >Much the same way that Velocity is a "value-add". > >I think the decision to further integrate OSxxx would depend on where the >integration point is. If it is outside the true core of WebWork (the >dispatcher), then I see it as a simple "value-add", and not important to >the "merging" discussion from a technical vantage point. I haven't looked >at the OSxxx technology, so I'm not sure where this integration point is. > > >From a community and exposure standpoint, I wonder who would be helping >whom more here. It really doesn't matter since there is good will involved >and the control of either project isn't in question. I'm not recommending >this, but if you wanted to extend your user base, it would be far more >"profitable" to team with the Apache group and the Velocity sub-project. >It's a kick-ass development environment when combined with WebWork, and I >get the feeling that its development community is far greater than OS and >WebWork combined. There are a lot of whack personalities over there, >though. > >jim > >_______________________________________________ >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 |