Community
Participate
Working Groups
The server testing framework for EclipseLink injects an entity manager using the defaults. This results in a transaction entity manager. The JPA tests are written in Java SE and expect an extended persistence context - with much more transactional control. This mismatch between assumptions needs to be corrected by either changing the test framework or the tests themselves. This mismatch results in a number of test errors that are difficult to diagnose and a number of bugs are being set as duplicates of this bug. When the issue is corrected, these tests should be rerun to see if there are still issues.
*** Bug 296747 has been marked as a duplicate of this bug. ***
*** Bug 296389 has been marked as a duplicate of this bug. ***
*** Bug 296388 has been marked as a duplicate of this bug. ***
*** Bug 296387 has been marked as a duplicate of this bug. ***
*** Bug 296381 has been marked as a duplicate of this bug. ***
*** Bug 296380 has been marked as a duplicate of this bug. ***
*** Bug 296376 has been marked as a duplicate of this bug. ***
Created attachment 158772 [details] patch for the bug
Clone an TestRunnerBean.java without EntityManager injected, all nonJTA datasource or application managed EntityManager inside container testing should this TestRunnerBean. Code Reviewed by Yiping Zhao. Checked in trunk, revision: 6579.
Need to back port to 2.0.2 after 2.0.1 release and the branch is open to check in.
Backport to 2.0.2, revision: 6634.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink