From an article by Sunil Patel @ http://www.javaworld.com/javaworld/jw-03-2008/jw-03-osgi1.html,
“The Open Services Gateway Initiative (OSGi), also known as the Dynamic Module System for Java, defines an architecture for modular application development. OSGi container implementations such as Knopflerfish, Equinox, and Apache Felix allow you to break your application into multiple modules and thus more easily manage cross-dependencies between them.
Similar to the Java Servlet and EJB specifications, the OSGi specification defines two things: a set of services that an OSGi container must implement and a contract between the container and your application. Developing on the OSGi platform means first building your application using OSGi APIs, then deploying it in an OSGi container. From a developer’s perspective, OSGi offers the following advantages:
You can install, uninstall, start, and stop different modules of your application dynamically without restarting the container.
Your application can have more than one version of a particular module running at the same time.
OSGi provides very good infrastructure for developing service-oriented applications, as well as embedded, mobile, and rich internet apps.
Given that you use servlet containers for building Web applications and EJB containers for building transactional applications, you may be wondering why you need yet another type of container. The short answer is that OSGi containers are intended specifically for developing complex Java applications that you want to break up into modules.”
- imabonehead: Developing enterprise OSGi applications for WebSphere Application Server (ibm.com)
- Java 8 gears up for the cloud (infoworld.com)