tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Costin Manolache" <>
Subject Re: Core webapps and clustering
Date Fri, 05 May 2006 15:09:06 GMT
As someone who used OSGI quite heavily in the past - I hope I'll
never have to touch it again :-), and certainly not in tomcat...
The _concept_ is good - components, dynamic binding, etc  - but OSGI is
a framework like all others, it wants the whole world to change to it's model.
Sort of an Avalon :-).

Regarding modularity - we already have a lot of modularity in the code, with
plenty of hooks and components. What we don't have is deployment modularity -
ability to package and deploy modules like cluster, connectors, valves
in a consistent

I also agree with Remy - we shouldn't be a Jboss/Geronimo clone - but
that doesn't
mean we shouldn't try to be more modular and support some of the good things in

JMX is currently the only API that I know that  allows this without
beeing a 'you have to
do it only my way' framework like osgi or avalon ( and so many more ).
Well, they do
have a bit of that - but so far modeler ( with all its problems ) was
able to shield us from
most of it.

So all I'm proposing is to just make small adjustments - fix modeler,
small packaging changes,
use modeler/jmx more for component configuration ( and less server.xml
/ tomcat-specific formats ).


On 5/5/06, Jess Holle <> wrote:
> Remy Maucherat wrote:
> > Henri Gomez wrote:
> >> May be not related, but did there is plan in TC 6.x to make use at
> >> some time OSGI framework, like the one used in Eclipse and RCP
> >> applications ?
> >>
> >> I really like this concept and it seems a good candidate to provide a
> >> modular kernel / micro-architecture.
> > If we do that, what doesn't make it a Geronimo clone ? The services
> > that are shipped by default, maybe ? ;)
> >
> > It also most likely make Tomcat more heavyweight, although I don't
> > know whether or not it would make it more difficult to integrate.
> As someone who really wants to integrate Tomcat into a larger
> application soon (I had a working prototype for a while), I really don't
> want Eclipse or its RCP -- or anything of the sort -- in Tomcat.
> I like the fact that Tomcat is still relatively lightweight and brings
> relatively few extra libraries and version conflicts thereof into the
> picture.  As long as I keep a few of the Apache libraries I use
> up-to-date, all is well (and probably would be otherwise -- it's just
> really easy to remove any possible issues by version matching).
> Future NetBeans versions may cease to embed Tomcat and embed the whole
> Glassfish thing instead, I don't know, but the embedding of Tomcat in
> current NetBeans releases is a perfect example of why no IDE's faddish
> RCP (Eclipse's, NetBeans', or new-sprocket-fad-xyz) should not make its
> way into Tomcat.
> [Sorry for any cynicism, but I've seen a rash of "wouldn't our simple,
> lightweight open source component X be oh so much better if we just
> stuck in an entire IDE framework underneath" knee jerks in open source
> communities ranging as far afield as jManage.  Let's K.I.S.S!]
> --
> Jess Holle
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
View raw message