Skip to main content
Jump to: navigation, search

Difference between revisions of "EclipseLink/Examples/OSGi/Equinox Byte Code Weaving"

m (Required Bundles)
m (Running Equinox)
Line 121: Line 121:
0      ACTIVE      org.eclipse.osgi_3.5.0.v20090513
0      ACTIVE      org.eclipse.osgi_3.5.0.v20090513
1      RESOLVED    org.eclipse.persistence.jpa.equinox.weaving_1.1.2.v20090519-r4244
1      RESOLVED    org.eclipse.persistence.jpa.equinox.weaving_2.1.0.v20100614-r7608
2      ACTIVE      org.eclipse.equinox.common_3.5.0.v20090513
2      ACTIVE      org.eclipse.equinox.common_3.5.0.v20090513
3      ACTIVE      javax.persistence_1.99.0
3      ACTIVE      javax.persistence_2.0.1.v201006031150
4      ACTIVE      org.eclipse.persistence.jpa_1.1.2.v20090519-r4244
4      ACTIVE      org.eclipse.persistence.jpa_2.1.0.v20100614-r7608
                     Fragments=5, 9
5       RESOLVED    org.eclipse.persistence.antlr_1.1.2.v20090519-r4244
5      RESOLVED    org.eclipse.persistence.jpa.osgi_2.1.0.v20100614-r7608
6      RESOLVED    org.eclipse.persistence.asm_1.1.2.v20090519-r4244
7      RESOLVED    org.eclipse.persistence.core_1.1.2.v20090519-r4244
8       RESOLVED    org.eclipse.persistence.jpa.equinox_1.1.2.v20090519-r4244
9      ACTIVE      my.example.jpa.bundle_1.0.0
6      RESOLVED    org.eclipse.persistence.antlr_2.1.0.v20100614-r7608
10      RESOLVED    org.apache.derby_10.1.2.1_v200803061811
7      RESOLVED    org.eclipse.persistence.asm_2.1.0.v20100614-r7608
8      RESOLVED    org.eclipse.persistence.core_2.1.0.v20100614-r7608
9      RESOLVED    org.eclipse.persistence.jpa.equinox_2.1.0.v20100614-r7608
10     ACTIVE      hello.jpa_1.0.0.200907091149
11     RESOLVED    org.apache.derby_10.1.2.1_v200803061811
You can see that that the fragment org.eclipse.persistence.jpa.equinox.weaving (1) has been successfully attached to the org.eclipse.osg (1) bundle.  You can also see that the fragment org.eclipse.persistence.jpa.equinox (8) has been attached to it's master org.eclipse.persistence.jpa (4).
You can see that that the fragment org.eclipse.persistence.jpa.equinox.weaving (1) has been successfully attached to the org.eclipse.osg (0) bundle.  You can also see that the fragment org.eclipse.persistence.jpa.equinox (9) has been attached to it's master org.eclipse.persistence.jpa (4).
== Confirming Byte Code Weaving is Working ==
== Confirming Byte Code Weaving is Working ==

Revision as of 16:16, 17 June 2010


Since EclipseLink 1.1.2 (Galileo), EclipseLink JPA byte code weaving is supported in Equinox OSGi. Configuration is straight forward and the requirements on your JPA persistence unit bundle are minimal.


Byte code weaving support is implemented through two fragments: org.eclipse.persistence.jpa.equinox.weaving and org.eclipse.persistence.jpa.equinox. o.e.p.j.equinox.weaving is a fragment for the system bundle org.eclipse.osgi. Extending the system bundle is a special case in OSGi and such a fragment is called a framework extension. This extension make use of the Equinox Adaptor Hook framework to hook into the byte code loading process and perform weaving when necessary. Configuring a framework extension is done using the standard OSGi osgi.framework.extensions property. This property needs to be declared either in your config.ini or on the commandline as:


o.e.p.j.equinox is a fragment for the org.eclipse.persistence.jpa bundle that registers byte code weavers for persistence units that require it. All that is necessary to enable this is to deploy it with your other bundles.


First create a root folder for the example, we'll refer to it as HOME.

NOTE: This example does not address how to develop an EclipseLink OSGi application in Eclipse PDE. It covers how to configure a runtime environment that supports byte code weaving for EclipseLink JPA. See Developing with EclipseLink OSGi in PDE to learn how to configure PDE and develop OSGi applications in Eclipse.

Required Bundles

  • Download Equinox to obtain the following bundles or copy them from an Eclipse IDE install's plugins folder and place them in HOME\plugins:
    • org.eclipse.equinox.common
    • org.eclipse.osgi
  • From the Equinox download page download the launcher appropriate for your operating system. The launcher comes in three parts: a native platform executable, a native platform library (packaged as an exploded bundle), and launcher jar. Copy both the launcher jar and native library folder to HOME\plugins. Copy the executable to HOME.
For example, for Win 32 you'll need to extract the following from the launcher zip:
  • From an Eclipse IDE install's plugins folder copy the following bundle to HOME\plugins:
    • org.eclipse.update.configurator
  • Download EclipseLink 1.1.2 (or above) and place the bundles into HOME\plugins
  • Place your JDBC driver bundle in HOME\plugins.
For example, you can download the Apache Derby database bundle org.apache.derby from the Eclipse Orbit download page. The Orbit bundle does not contain the client driver so you would be limited to an embedded database. Note that when using an embedded database only one process can have the database open at a time. Here's an example of the EclipseLink login and config settings for an embedded Derby database:
<property name="" value="Derby"/>
<property name="javax.persistence.jdbc.driver" value="org.apache.derby.jdbc.EmbeddedDriver"/>
<property name="javax.persistence.jdbc.url" value="jdbc:derby:comics;create=true"/>
<!-- Setting read and write pool mins to 1 will reduce the initial number of connections. -->
<property name="" value="1"/>
<property name="eclipselink.jdbc.write-connections.min" value="1"/>

Enabling Byte Code Weaving in your Application

The following requirements must be met to enable byte code weaving on your Entities:

  1. Provide class loader to Persistence.createEntityManagerFactory
  2. The org.eclipse.persistence.jpa bundle must be required by your bundle
  3. Explicitly indicate you want byte code weaving in your persistence.xml

Passing Class Loader

Access to the classloader that loads your Entities is required by EclipseLink. In your application you need to pass this classloader as a property to Persistence.createEntityManagerFactory(). Failure to provide the classloader will result in a failure.

import org.eclipse.persistence.config.PersistenceUnitProperties;
Map<String,Object> properties = new HashMap<String, Object>();
properties.put(PersistenceUnitProperties.CLASSLOADER, this.getClass().getClassLoader());
emf = Persistence.createEntityManagerFactory("comics", properties);

Require org.eclipse.persistence.jpa

In the of your application bundle, you need to require the org.eclipse.persistence.jpa bundle. Note that the minimum version that supports byte code weaving in OSGi is 1.1.2 (Galileo).

Require-Bundle: org.eclipse.persistence.jpa;bundle-version="1.1.2"

Enable Weaving in persistence.xml

Typically, byte code weaving is automatically enabled by EclipseLink based on what environment it's running in. For example, in a Java EE5 container byte code weaving is always enabled. In Equinox, byte code weaving is not automatically enabled. If you have configured your Equinox runtime target correctly, you can go ahead and indicate that you want byte code weaving to be performed.

<property name="eclipselink.weaving" value="true"/>

Equinox Configuration

When running Equinox with a launcher you define your configuration in a config.ini file which must be placed in HOME\configuration. Here are the features of note in an example config.ini below:

  1. osgi.bundles.defaultStartLevel is set to 6 so that all the bundles that should be started will be started in an unambiguous order.
  2. osgi.framework.extensions identifies the framework extension org.eclipse.persistence.jpa.equinox.weaving. This is critical for byte code weaving.
  3. org.eclipse.equinox.common and org.eclipse.update.configurator are started as per the instructions in the Equinox Quickstart.
  4. javax.persistence is started before org.eclipse.persistence.jpa so that it can start up a service tracker to listen for JPA provider services.
  5. org.eclipse.persistence.jpa is started before user bundles so that it may register itself as a JPA persistence provider.
  6. my.example.jpa.bundle (or whatever you call your JPA bundle) is auto-started.
  7. The JDBC driver bundle (e.g., org.apache.derby) is deployed but started. Check the documentation of your driver to see if it must be started
osgi.bundles= \
 org.eclipse.equinox.common@2:start, \
 org.eclipse.update.configurator@3:start, \
 javax.persistence@4:start, \
 org.eclipse.persistence.jpa@5:start, \
 org.eclipse.persistence.antlr, \
 org.eclipse.persistence.asm, \
 org.eclipse.persistence.core, \
 org.eclipse.persistence.jpa.equinox, \
 my.example.jpa.bundle@start, \

Running Equinox

With the required bundles in the HOME\plugins folder and config.ini in the HOME\configuration folder you're ready to start your application. On Windows, you can start Equinox by using running the native "launcher.exe" program from the HOME folder. During development it's recommended you run with the "-clean" option to clear caches between runs. The "-console" option can be used to interact with Equinox. This is especially useful when things aren't working as expected.

> launcher -clean -console

If launched with -console, you can examine the state of your bundles using the ss command. You should see something like:

osgi> ss

Framework is launched.

id      State       Bundle
0       ACTIVE      org.eclipse.osgi_3.5.0.v20090513
1       RESOLVED    org.eclipse.persistence.jpa.equinox.weaving_2.1.0.v20100614-r7608
2       ACTIVE      org.eclipse.equinox.common_3.5.0.v20090513
3       ACTIVE      javax.persistence_2.0.1.v201006031150
4       ACTIVE      org.eclipse.persistence.jpa_2.1.0.v20100614-r7608
                    Fragments=5, 9
5       RESOLVED    org.eclipse.persistence.jpa.osgi_2.1.0.v20100614-r7608
6       RESOLVED    org.eclipse.persistence.antlr_2.1.0.v20100614-r7608
7       RESOLVED    org.eclipse.persistence.asm_2.1.0.v20100614-r7608
8       RESOLVED    org.eclipse.persistence.core_2.1.0.v20100614-r7608
9       RESOLVED    org.eclipse.persistence.jpa.equinox_2.1.0.v20100614-r7608
10      ACTIVE      hello.jpa_1.0.0.200907091149
11      RESOLVED    org.apache.derby_10.1.2.1_v200803061811


You can see that that the fragment org.eclipse.persistence.jpa.equinox.weaving (1) has been successfully attached to the org.eclipse.osg (0) bundle. You can also see that the fragment org.eclipse.persistence.jpa.equinox (9) has been attached to it's master org.eclipse.persistence.jpa (4).

Confirming Byte Code Weaving is Working

You can test to see if byte code weaving was successful by checking to see if your entities implement the EclipseLink PersistenceWeaved interface.

import org.eclipse.persistence.internal.helper.Helper;
import org.eclipse.persistence.internal.weaving.PersistenceWeaved;
if (Helper.classImplementsInterface(MyEntity.class, PersistenceWeaved.class)) {
   // MyEntityEntity successfully woven!

Back to the top