Community
Participate
Working Groups
There are the following 13 JPA2.0 tests in advanced test suite running and failed on JBoss 5.0.1.GA and 5.1.0.GA: jpa.advanced.EntityManagerJUnitTestSuite.testDetachNull testDetachRemovedObject testLockingLeftJoinOneToOneQuery testLockingLeftJoinOneToOneQuery2 testGetProperties testDetachNonEntity testFindWithProperties testDetachManagedObject testDetachNonManagedObject testGetLockModeType testGetEntityManagerFactory testUnWrapClass jpa.advanced.AdvancedJPAJunitTest.testMetamodelMinimalSanityTest There is a flag "isJPA10" was introduced in the test framework (JUnitTestCase.java), and all those tests should run on any server that not supporting JPA2.0. All those tests didn't run on WLS/WAS/OC4J/Glassfish, but not sure what happened, they all ran on JBoss server even though there isn't JPA2.0 preview persistence.jar in the classpath, so all those tests failed on JBoss. Need to investigate the class loading for JBoss server during run time.
Add flag "isJPA10()" in test suite level to skip all JPA2.0 tests on only JPA1.0 supported application servers, e.g. JBoss-5.1.0.GA, GlassFish-v2, WLS-10.3.3 and previous versions. Code reviewed by Yiping Zhao. Checked in trunk (2.2.0), revision: 7870. Back port to 2.1.1, revision: 7871
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink