Eclipse Community Forums: Gemini » Gemini JPA 1.0 Milestone 2

Help

Home

Home » Eclipse Projects » Gemini » Gemini JPA 1.0 Milestone 2

Show: Today's Messages :: Show Polls :: Message Navigator

Gemini JPA 1.0 Milestone 2 [message #633258]

Fri, 15 October 2010 21:26

Michael Keith

Messages: 243
Registered: July 2009

Senior Member

We are pleased to announce that Gemini JPA 1.0 Milestone 2 is currently available from the download page.

Please raise any issues or questions you may have with it on the forum.

-Mike

Report message to a moderator

Re: Gemini JPA 1.0 Milestone 2 [message #633340 is a reply to message #633258]

Sat, 16 October 2010 18:09

David Schmitz

Messages: 6
Registered: October 2010

Junior Member

Hi Mike,

I am currently trying to get Gemini JPA 1.0.0 M2 to work with EclipseLink 2.1.1 but I get the following error message and can't make any clue out of it. That means whether i have forgotten something or if this is a bug:

[EL Config]: 2010-10-16 20:07:13.725--The access type for the persistent class [class com.navteq.phoenix.target.engine.jpa.model.TargetStatus] is set to [FIELD].
[EL Config]: 2010-10-16 20:07:13.747--The alias name for the entity class [class com.navteq.phoenix.target.engine.jpa.model.TargetStatus] is being defaulted to: TargetStatus.
[EL Config]: 2010-10-16 20:07:13.749--The table name for entity [class com.navteq.phoenix.target.engine.jpa.model.TargetStatus] is being defaulted to: TARGETSTATUS.
[EL Config]: 2010-10-16 20:07:13.761--The column name for element [field id] is being defaulted to: ID.
[EL Config]: 2010-10-16 20:07:13.762--The column name for element [field startTimeStamp] is being defaulted to: STARTTIMESTAMP.
[EL Config]: 2010-10-16 20:07:13.762--The column name for element [field status] is being defaulted to: STATUS.
[EL Config]: 2010-10-16 20:07:13.762--The column name for element [field targetGraphName] is being defaulted to: TARGETGRAPHNAME.
[EL Config]: 2010-10-16 20:07:13.763--The column name for element [field targetName] is being defaulted to: TARGETNAME.
[EL Config]: 2010-10-16 20:07:13.763--The column name for element [field finishTimeStamp] is being defaulted to: FINISHTIMESTAMP.
!SESSION 2010-10-16 20:07:12.416 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.6.0_21
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=de_DE
Command-line arguments: -dev file:/home/dschmitz/devel/workspace/.metadata/.plugins/org.e clipse.pde.core/Phoenix JPA Gemini/dev.properties -os linux -ws gtk -arch x86_64 -consoleLog

!ENTRY org.eclipse.osgi 4 0 2010-10-16 20:07:13.792
!MESSAGE An unexpected runtime error has occurred.
!STACK 0
java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method " $Proxy1.createEntityManagerFactory(Ljava/util/Map;)Ljavax/pe rsistence/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:23 89)
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.registerEMFSe rvices(PersistenceServicesUtil.java:205)
at org.eclipse.gemini.jpa.provider.EclipseLinkOSGiProvider.regi sterPersistenceUnits(EclipseLinkOSGiProvider.java:244)
at org.eclipse.gemini.jpa.PersistenceBundleExtender.registerPer sistenceUnitsInBundle(PersistenceBundleExtender.java:223)
at org.eclipse.gemini.jpa.PersistenceBundleExtender.bundleChang ed(PersistenceBundleExtender.java:278)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.d ispatchEvent(BundleContextImpl.java:919)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEv entSynchronous(ListenerQueue.java:149)
at org.eclipse.osgi.framework.internal.core.Framework.publishBu ndleEventPrivileged(Framework.java:1349)
at org.eclipse.osgi.framework.internal.core.Framework.publishBu ndleEvent(Framework.java:1300)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWor ker(BundleHost.java:356)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resu me(AbstractBundle.java:374)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBun dle(Framework.java:1067)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:561)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.r esumeBundles(StartLevelManager.java:546)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.i ncFWSL(StartLevelManager.java:459)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.d oSetStartLevel(StartLevelManager.java:243)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.d ispatchEvent(StartLevelManager.java:440)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEve nt(EventManager.java:227)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread .run(EventManager.java:337)

Is this a bug or is it caused by wrong configuration?

Report message to a moderator