Re: JPA API compatibility in 1.2/2.0

> 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)
>>
>>
>>
>