New OSGi spec eases Java use in runtime

Anyway, requirements raised by the JSR expert group resulted in modifications to the core OSGi specification. So now JSR 291 corresponds to the reference implementation based on the Eclipse Equinox open source project, as well as technology compatibility kit (TCK) to check for JSR 291 compliance. The OSGi Alliance will also offer the JSR 291 TCK at no charge to qualified non-profit organizations.

The OSGi Alliance has released the latest specification for Java SE/EE, promising enterprise users the same agility and management capability that mobile apps have had since last fall.

OSGi Service Platform Release 4 Core Specification Version 4.1, the result of JSR 291, provides a framework for packaging Java applications as independent modules, thus allowing users to install, execute, update, and remove Java and associated components without restarting the JVM and disrupting operations.

The request for the specification noted that these capabilities were brought into the mobile apps community through JSR 232, which was given final approval last October. The request was for a specification to enable components to be declared through metadata and be assembled at runtime using a class loader delegation network.

The proposed specification went for public review in December of 2006 and the approval process was completed May 21.

This sure seems like a logical development. Wonder why it took so long?

Anyway, requirements raised by the JSR expert group resulted in modifications to the core OSGi specification. So now JSR 291 corresponds to the reference implementation based on the Eclipse Equinox open source project, as well as technology compatibility kit (TCK) to check for JSR 291 compliance. The OSGi Alliance will also offer the JSR 291 TCK at no charge to qualified non-profit organizations.

The JSR 291 specification can be downloaded.