On Sun, Dec 21, 2008 at 12:39 AM, Dan Creswell <d...@dcrdev.demon.co.uk> wrote:

> OSGI has a classloader model similar to Jini's (highly granular and
> compartmentalized, possibly better documented as well) and one might
> indeed manage a port to that model but any container that doesn't do
> OSGI will still not work right.  I have seen similar approaches to Ron
> Mann's to solve this OSGI/Container integration problem via a bridge
> servlet.  So I guess if you ported Jini to that model you could save
> yourself a package (Ron's) but that's about it.

Well, there are two aspects;

 1. As you mentioned, it is not very hard to make OSGi work in a
container. That is largely due to the fact that OSGi do complete class
isolation from parents (although one can override this on a package by
package level). So, if Jini works in OSGi, OSGi works in Tomcat and we
are in a much better position.

 2. A LOT of the Java EE containers are moving to OSGi; JoNAS,
Geronimo, GlassFish, JBoss and WebLogic. It is a matter of time when
they all use it. BUT, and there is a catch, all except JoNAS doesn't
expose OSGi as a programming model to the applications they host, so
one can not 'just deploy' OSGi based apps. Personally, I think this
will also change over time, but it is not around the corner.


Cheers
Niclas

Reply via email to