Community
Participate
Working Groups
Going forward we will need to ensure that we can support deploying against a 1.0 compliant application server using new EclipseLink versions with JPA 2.0 support. As a start WebLogic and GlassFish should be supported. We will also need to ensure that a JPA 2.0 application can be deployed against a JPA 1.0 compliant container using the new EclipseLink libraries.
See http://wiki.eclipse.org/index.php?title=EclipseLink/Development/JPA2.0/container_support
Changing priority to P@ since JPA 2.0 features are required for the 2.0 release
QA has implemented Server tests that test JPA 2.0 functionality within WLS's JPA 1.0 container.
It has been reported that QA is changing the System classpath of the Application server when running tests. This would be an option of last resort and so this bug is being reopened.
Moving these bugs to 2.0.1 since 2.0 is shipping today. If the issue is resolved for 2.0 please change the target back when you close the bug.
Moved to 2.1 as dependant bug is assigned to 2.1
>both open bug# 296383 and bug# 308477 are future - pushing parent bug to future
>JBoss 6.0.0M2 now supports JPA 2.0 and should be verified However the tutorial was recently updated when JBoss 6.0.0M1 came out for JPA 2.0 functionality - and is OK https://bugs.eclipse.org/bugs/show_bug.cgi?id=250477#c3
>JPA 2.0 on WebLogic 10.3 and GlassFish V2 and V3 support pages at http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/glassfish http://wiki.eclipse.org/EclipseLink/Development/JPA_2.0/weblogic >JPA 2.0 on OC4J newsgroup request http://forums.oracle.com/forums/message.jspa?messageID=4406027#4406027
>GlassFish and WebLogic details are on the wiki pages above
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink