Ian Robinson starts with the problems of basic JAR level deployment: lack of encapsulation, versioning and missing classes are not discovered until runtime. Then the problems specific to JEE: duplication of utility JARs across applications, version dependency conflicts. Then quick overview of the OSGi package resolution mechanism and how it can address these challenges.
Changes in the political landscape to allow OSGi enterprise applications to be deployed to commercial runtimes: e.g. Apache Geronimo, JBoss, WebSphere.
Feature pack can deploy existing EARs as OSGi Bundles. Common utility libraries are extracted and deployed into the Bundle repository.
Apache Aries Blueprint container can inject JPA contexts into beans, either using annotations or using XML wire-up declared in a Blueprint file.
Enterprise Bundle Application (EBA): a packaging/deployment unit for OSGi applications. You can choose to package content and then refer to external Bundles that will be loaded from the bundle repository. The life-cycle of resolving and freezing the deployment -- the resolver can save its state to ensure that the bundles that were resolved on a test system and also used (exactly) on a production system.
The feature pack includes a blog example that illustrates the major features of enterprise OSGi, including JPA, transactions, a web app etc. The admin console allows your to browse the bundles deployed on WAS remotely, using an interface similar to the Equinox command line client.
You can upload new versions of external bundles into the bundle repository. The WAS admin console will display the newer version and allow the admin to update the application with the newer bundle (including previewing the resolution first). When the application is restarted the newer version of the external dependency will be used.
OSGi services can be exposed as SCA components.
Eclipse plugins (requires Eclipse 1.6 WTP M6 or later) to edit Blueprint and EBA files. Available standalone or within the latest RAD beta.