Description Krum Tsvetkov 2010-10-25 03:26:15 EDT

Hi,

The bundle org.eclipse.gemini.javax.persistence has inside the javax.persistence API. This leads to troubles with classloading (see exception below) if the API is already existing in the OSGi environment. EclipseLink has its own javax.persistence bundle and having both doesn't work. At least not always (depends somehow on the startup order).

If I remove either javax.persistence (coming with EclipseLink) or org.eclipse.gemini.javax.persistence (coming with Gemini JPA), then my samples work. However, both bundles contain not only the API, but some classes from the projects. 

Will it be possible to extract the "pure" javax.persistence api out of the org.eclipse.gemini.javax.persistence bundle and declare a dependency on it?

Here is the concrete error I am facing.

java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "$Proxy1.createEntityManagerFactory(Ljava/util/Map;)Ljavax/persistence/EntityManagerFactory;" the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) of the current class, $Proxy1, and the class loader (instance of org/eclipse/osgi/internal/baseadaptor/DefaultClassLoader) for interface org/osgi/service/jpa/EntityManagerFactoryBuilder have different Class objects for the type javax/persistence/EntityManagerFactory used in the signature
	at java.lang.Class.getDeclaredConstructors0(Native Method)
	at java.lang.Class.privateGetDeclaredConstructors(Class.java:2389)
	at java.lang.Class.getConstructor0(Class.java:2699)
	at java.lang.Class.getConstructor(Class.java:1657)
	at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:587)
	at org.eclipse.gemini.jpa.PersistenceServicesUtil.registerEMFServices(PersistenceServicesUtil.java:205)
	at org.eclipse.gemini.jpa.provider.EclipseLinkOSGiProvider.registerPersistenceUnits(EclipseLinkOSGiProvider.java:244)
	at org.eclipse.gemini.jpa.PersistenceBundleExtender.registerPersistenceUnitsInBundle(PersistenceBundleExtender.java:223)
	at org.eclipse.gemini.jpa.PersistenceBundleExtender.bundleChanged(PersistenceBundleExtender.java:278)
	at org.eclipse.osgi.framework.internal.core.BundleContextImpl.dispatchEvent(BundleContextImpl.java:919)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
	at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:149)
	at org.eclipse.osgi.framework.internal.core.Framework.publishBundleEventPrivileged(Framework.java:1349)
	at org.eclipse.osgi.framework.internal.core.Framework.publishBundleEvent(Framework.java:1300)
	at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:356)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:284)
	at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:276)
	at org.eclipse.osgi.framework.internal.core.FrameworkCommandProvider._start(FrameworkCommandProvider.java:252)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.eclipse.osgi.framework.internal.core.FrameworkCommandInterpreter.execute(FrameworkCommandInterpreter.java:155)
	at org.eclipse.osgi.framework.internal.core.FrameworkConsole.docommand(FrameworkConsole.java:156)
	at org.eclipse.osgi.framework.internal.core.FrameworkConsole.runConsole(FrameworkConsole.java:141)
	at org.eclipse.osgi.framework.internal.core.FrameworkConsole.run(FrameworkConsole.java:105)
	at java.lang.Thread.run(Thread.java:619)|