JPA 2.0 in JDeveloper 11.1.2.3

Question

Hello,
I'm having some difficulties using a newer version of eclipselink and JPA 2.0 in JDeveloper 11.1.2.3, and I was hoping someone has done this before and could shed some light onto what I'm doing wrong.
In my weblogic-application.xml file, I added the following:
<prefer-application-packages>
<package-name>org.eclipse.persistence.*</package-name>
</prefer-application-packages>
This successfully made the application use the newer version of eclipselink at runtime that I have included with the application and added in the "Libraries and Classpath" section of my project.
However, I have been unsuccessful at compiling with the JPA 2.0 jar. I added the JPA 2.0 jar to the classpath the same way, but within JDeveloper it keeps trying to compile against the 1.0 jar that is included by default. I even removed the "Toplink" library from the classpath that JDeveloper added automatically, so I'm not sure where it's still picking up the old jar from.
I found the following information about how to enable JPA 2.0 support on the weblogic server (http://docs.oracle.com/cd/E23943_01/web.1111/e13720/using_toplink.htm#CIHDJHHI), but that is only relevant after the application can actually compile.
Anyone have any ideas?
Thanks!

Answer 1

Turns out this was due to how JDeveloper was assembling the compile commands. The project that is using JPA had a dependency on another project in the application that was including the JPA 1.0 jar as part of the ADF libraries it was using, and JDeveloper was putting the classes for that project and all of its dependencies ahead of any jars defined in the classpath for the project using JPA 2.0. Thus, at compile time, the JPA 1.0 jar was the first one found in the classpath, causing the compilation to fail.
After working around this, and following the instructions here (http://docs.oracle.com/cd/E23943_01/web.1111/e13720/using_toplink.htm#CIHDJHHI) to update the weblogic classpath to use JPA 2.0 at runtime, I receive the following message in the logs:
This version of OpenJPA cannot read a persistence.xml document with a version different from "1.0". Found: version "2.0" in "file:/C:/Users....."
Everything appears to work fine as the JPA 2.0 methods are being executed with eclipselink, but this message appears every time I grab an EntityManager. Is this the expected behavior, or is there a step missing in the instructions?
Thanks!