OSGI vs GBeans

当年 jboss app server利用jmx来组织、管理各个子系统

geronimo作为后来者在jmx的基础上设计出了Gbeans来组织、管理各个子系统

osgi作为通用的bundle框架已经被eclipse glassfish3 openejb3等软件采用，并将进入jdk(jsr 277),还出现了一些如jsr 291 294等等的标准

不知道geronimo还要在gbeans上扛多久,持久化的方案已经用openjpa代替TranQL,拥抱标准有好处，不过要是基础设施也替换的话工作量会不小，而且没有卖点了，众app server都是建立在osgi上，而且都开源。。



http://tp.its.yale.edu/confluence/display/TP/Geronimo

Which leaves an opening for a smaller, more agile project to leapfrog over these leading older servers. JOnAS 5, for example, will adopt an OSGi microkernel instead of the "old" JBoss JMX microkernel. Eclipse has demonstrated the power of OSGi, but then the Eclipse IDE seems to be many, many times more complicated than even a J2EE 5 server. On paper there are advantages to the new technology, but a middleware server suite may not find many practical benefits.

Geronimo has a microkernel with GBeans (instead of JBoss JMX MBeans). GBeans are not OSGi, which is a technology for bundling JAR files and managing the visibility of packages through ClassLoaders. All that is useful, but GBeans (like MBeans and Spring technology) provides container managed objects and not just classpath management. What is new here (compared to MBeans) is that a reference to objects created by the container is inserted where needed through dependency injection.