My name is Sébastien Arbogast, I’m 27 and I’m a freelance Software Architect and Developer based in Brussels, Belgium. My main specialties are agile methodologies, rich internet application, highly productive Java development and iPhone development. Sebastien is a DZone MVB and is not an employee of DZone and has posted 26 posts at DZone. You can read more from them at their website. View Full User Profile

JBoss is working on OSGi too

  • submit to reddit
I wanted to download the latest version of JBoss AS to deploy it to a new server, and while I was wandering round their site to see what is going on, I found an interview of Ales Justing by Mark Newton about the work they’re doing with OSGi.

Apparently they are not waiting for it to happen. They’re really taking part in it, which is refreshing because ever since Redhat acquired them, I’ve always been afraid of the possibility that they could rest on their achievements and have trouble keeping up with innovation. Obviously I was wrong and since they even have some people inside the Enterprise Expert Group, we can expect some pretty good integration of OSGi into future releases of JBoss.

They are even going as far as reengineering a key part of their architecture, which is the microcontainer, to integrate OSGi. That’s really an excellent thing because I’ve always found that JMX is really a pain to manage. According to the interview, they are totally changing their core classloader:

We could probably use the classloading features of existing OSGi frameworks but it would again mean bending around things to make them work. As we wanted to have a bullet proof implementation, where all the nasty details were hidden away under private/protected modifiers, it was important that we could tightly control access through policies and delegation. From this perspective it made more sense to implement our own classloading layer.

Concerning integration with Spring, apparently they are still taking their distances. I guess it has something to do with the fact they Spring/Hibernate competes with EJBs and has thus encouraged many developers to choose a simple Tomcat server instead of a full-blown JBoss for their deployment. But as long as I can freely deploy my Spring/Hibernate on JBoss and still benefit from features like SOAP, JNDI, JMS and so on, that’s fine with me.

So that’s one other major actor of the enterprise application server market who is moving towards OSGi. Did I already say that it’s going to be big? And OSGi DevCon is certainly going to be very important this year.

Published at DZone with permission of Sebastien Arbogast, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)


Fred Grott replied on Tue, 2008/02/12 - 7:30am

 Ahem, noit waiting for it to happen after being somehwat later than Apache Geronimo having OSGi implemented in a JavaEE5 certified compliant server?? Surely you must be joking..?? JBOss MicoKernel was rewritten to handle OSGi as OSGi was not their first choice..


Compare the 2005-2006 writings about the JBoss5 Microkernel to the writings now..


Fred Grott(aka shareme) sometimes a JavaZone(JavaLobby) and EclipseZone contributor. Top visited blog on at:

Sebastien Arbogast replied on Tue, 2008/02/12 - 9:29am

But at that time, there was absolutely no move of OSGi towards server-side stuff, at least not that I know of. The Enterprise Expert Group has only started working in early 2007. So I guess JBoss did the best they could with what was mature at that time. I agree that OSGi is generic enough so it could have seen server-side usage before, and I'm still wondering why it's taking off now. My point is that they could have let others create their own mainstream implementations first and then incorporate it, as they did with Tomcat in the first place. But they didn't.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.