JPA API compatibility in 1.2/2.0
|
View:
New views
3 Messages
—
Rating Filter:
Alert me
|
 |
JPA API compatibility in 1.2/2.0
by Syvalta
::
Rate this Message:
Hi,
I have succesfully used EclipseLink 2.0-M7 in app server containing JPA1 API. After updating to 2.0-M8 my application no longer deploys. Is 2.0 supposed to work under JPA1 API or should I use 1.1.x (also 1.2 seem to be JPA2)? The stack trace if as follows (seems that eclipselink.jar bundles some of the JPA 2.0 API classes but not spi): java.lang.NoClassDefFoundError: javax/persistence/spi/ProviderUtil at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:621) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$000(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at javax.persistence.Persistence.findAllProviders(Persistence.java:186) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:103) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83) |
|
|
Re: JPA API compatibility in 1.2/2.0
by Syvalta
::
Rate this Message:
Actually, it seems that the latest 2.0-SNAPSHOT already contains the missing classes.
|
|
|
Re: JPA API compatibility in 1.2/2.0
by tware
::
Rate this Message:
You are correct.
There was an issue when we did an update of the JPA API to the latest specification version. It is resolved in the latest nightly builds. -Tom Syvalta wrote: > Actually, it seems that the latest 2.0-SNAPSHOT already contains the missing > classes. > > > > Syvalta wrote: >> Hi, >> >> I have succesfully used EclipseLink 2.0-M7 in app server containing JPA1 >> API. After updating to 2.0-M8 my application no longer deploys. Is 2.0 >> supposed to work under JPA1 API or should I use 1.1.x (also 1.2 seem to be >> JPA2)? >> >> The stack trace if as follows (seems that eclipselink.jar bundles some of >> the JPA 2.0 API classes but not spi): >> >> java.lang.NoClassDefFoundError: javax/persistence/spi/ProviderUtil >> at java.lang.ClassLoader.defineClass1(Native Method) >> at java.lang.ClassLoader.defineClass(ClassLoader.java:621) >> at >> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) >> at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) >> at java.net.URLClassLoader.access$000(URLClassLoader.java:56) >> at java.net.URLClassLoader$1.run(URLClassLoader.java:195) >> at java.security.AccessController.doPrivileged(Native Method) >> at java.net.URLClassLoader.findClass(URLClassLoader.java:188) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:307) >> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) >> at java.lang.ClassLoader.loadClass(ClassLoader.java:252) >> at javax.persistence.Persistence.findAllProviders(Persistence.java:186) >> at >> javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:103) >> at >> javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:83) >> >> >> > eclipselink-users mailing list eclipselink-users@... https://dev.eclipse.org/mailman/listinfo/eclipselink-users |
| Free embeddable forum powered by Nabble | Forum Help |
