Importing Javax.Persistence 2.0
In March of 2010, the OSGi Alliance released the OSGi Enterprise Specification which defines how a number of Java EE technologies including JPA can be used within OSGi. One issue raised by this specification is how to identify each API version as Java EE numbering is not based on the same strict rules as OSGi. For example, by the OSGi versioning rules JPA 2.0 should really be 1.1 as it is fully backwards compatible with JPA 1.0 and adds additional API. The Gemini project (based on EclipseLink) is building the Enterprise OSGi JPA spec implementation and will provide support for JPA 1.1 (OSGi numbering) but will tag each package export with a "jpa" attribute to allow importers to specify the Java EE specification number independent of the OSGi version.
So, to use JPA 2.0 in OSGi you would use the following import package declaration:
Prior to the definition of the OSGi Enterprise specification, EclipseLink shipped a JPA 2.0 preview bundle versioned as 1.99, but without a jpa attribute specified. By specifying jpa="2.0" you can ensure that the preview bundle is not used even when you specify the OSGi Enterprise spec JPA version of 1.1.0.
Examples that illustrate the use of EclipseLink in OSGi applications
- Developing with EclipseLink OSGi in PDE
- Equinox Byte Code Weaving
- Using EclipseLink JPA in an RCP application
Eclipse Rich Client Platform (RCP)
Examples that show how to use EclipseLink in RCP Applications.