After reading this article, one question came to my mind: 'Is OSGi becoming a J2EE? Is OSGi going to replace J2EE? Is OSGi incrementing J2EE?' It's true that historically OSGi is totally different from J2EE, but considering now the resulting work from the EEG, some of these services are J2EE services. Another fact is that who uses J2EE uses it for its APIs in contradiction to OSGi which is supposed to be API agnostic. I am not sure where is it going to get, what about you guys?
+1
A:
Take a look at InfoQ article about new buzzword JOSH: A Proposed Software Stack for the Enterprise. There is no J2EE at all. Only JSON, OSGi, Scala and HTTP. It's quite interesting...
gedevan
2009-03-27 08:57:52
+2
A:
OSGi is the container technology. It has nothing to do with J2EE technologies like (for example) Servlets, JDBC, EJBs, JMS etc.
It looks after the packaging of the code components (into bundles) and the management thereof. That may impact how you package a solution (e.g. you may not use a .ear or a .war) but the APIs you're used to programming to won't change.
Brian Agnew
2009-03-27 10:51:39
but J2EE containers are also called "containers", aren't they? There is definitely an amount of overlap. Spring DM Server is n OSGI alternative to packaging enterprise applications. There are also issues with Hibernate, see http://stackoverflow.com/questions/662986/osgi-hibernate, so I'd say the question is spot-on.
Dan
2010-09-03 18:20:42
+2
A:
It already exists if you want to try it: IBM WebSphere Application Server 6.1: Componentization Overview. I thought BEA and JBoss implementations were in the works, but I haven't heard anything recently.
OSGi won't be a replacement for J2EE - it extends it by adding a plugin framework. Whether it becomes part of a future J2EE standard probably depends on what happens with any Sun acquisition, the future of Project Jigsaw (replacement for JSR 277), and probably a few factors I don't know about. There aren't any plans for JEE6, except to cross fingers and hope something makes it into Java Standard Edition 7.
McDowell
2009-03-27 10:53:59
A:
OSGi is not becoming J2EE... I'm not sure what that would even mean! It is adding features that help to migrate J2EE code more smoothly to OSGi. But they are optional features, there is no need to use them if you do not have J2EE legacy.
Perhaps a better question is whether OSGi will become the widely accepted deployment container for Java applications, as J2EE once was. IMHO the answer is clearly yes.
Neil Bartlett
2009-10-29 23:45:11