tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Costin Manolache" <>
Subject Re: Osgifing Tomcat
Date Wed, 23 Apr 2008 15:30:36 GMT
Well, adding OSGI-compatible manifests to the existing jars is not
that intrusive,
and could be easily done in the trunk. AFAIK an Activator is not required - i.e.
if you don't need the BundleContext or to add services, you can have a bundle
that just imports/exports packages.

I agree with Remy that any 'intrusive' part of OSGI should be avoided
and certainly
not be done in trunk - changing existing packaging shouldn't be done
just because
OSGI requires a separate bundle for API and impl.

Now - the really interesting part is not how to package tomcat to be
used inside OSGI,
but how to have tomcat use OSGI modules ( and package webaps as bundles ), and
how to do this in a non-intrusive way. It looks like felix has a
mode, it would be interesting to see if it can be used, so all
configuration stays inside


On Wed, Apr 23, 2008 at 7:49 AM, Remy Maucherat <> wrote:
> On Wed, 2008-04-23 at 16:00 +0200, Florent.BENOIT wrote:
>  > Also, for OSGi, as all is done by package (import/export) the first step
>  > is to be sure that API and Implementation are never in the same package
>  > name. So we can export APIs and keep private the implementation.
>  I think the first main problem with these frameworks is how intrusive
>  they are, esp compared with whet they provide :( I suppose there's no
>  problem with doing a tomcat-osgi in the sandbox if people want to. As I
>  said I really don't care.
>  Rémy
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail:
>  For additional commands, e-mail:
View raw message