Community
Participate
Working Groups
This bug is originated from a bug for TopLink in Oracle bug base. (James Sutherland) Many of the JPA tests have been written to make debugging of failures more difficult. - Many of the tests begin a transaction, but do not put the commit/rollback in a finally (and never close the EntityManager) this will lead to a cascading of failures if one of these tests fail. i.e. many test in EntityManager test suite. - Many of the tests are dependent on previous tests running successfully, i.e. update tests depends on insert test running before it, and delete test depends on update test running, test should only be dependent on the Suite setup, never other tests. i.e. inherited tests - Some of the tests create the suite from the test class, this does not give consistent test ordering, which can cause inconsistent and difficult to debug failures. i.e. entity manager test suite. - Many of the tests cannot be run twice in a row, i.e. DDL tests, XML merge tests. A few tests were fixed to define consistent ordering to run in the server, but for the most part all of the above are still issues.
This bug fix did not make the cut off for 2.0.0. We are deferring the bugs to Future where we can properly sort them all together based on community votes and severity. We will then assign them accordingly to future patch sets and releases.
Changing the priority of the bugs that have been recently triaged to future. Targetting them to P2 will differentiate them from the P3s that have been triaged into future earlier.
>The tests currently run in the testing browser individually ok (although a couple must be run in order - especially testSetup() >The tests actually are designed to make debugging in the Eclipse IDE easier debug traces, in-place variable substitution, method modify/auto-rerun etc.. You may reference the design docs and bug comments for the results of above >The suites are re-runable. I regulary run test-jpa, test-core on derby, db2 with the same results - it may be Oracle that has an existing table issue. >The originator of this bug may reraise this with specific details -as the suites have changed a lot in the last 2 years. moving the bug from P2 to P4
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
