Community
Participate
Working Groups
This bug is originated from a bug for TopLink in Oracle bug base. (James Sutherland) None of our JPA tests verify what was written (inserted/updated) was actually persisted correctly to the database. They only verify that no errors occurred. At the end of any create/update test the test should clear the cache and re-read the object and compare it with what was written. This should be made into a generic method on JUnitTestCase so the tests only need to call this. i.e. verifyObject(object) - clearCache - readObject - session.compareObjects Ideally the compareObjects method would be updated to include comparison to casacaded mappings (i.e. private and cascade persist). Also verifyDelete should also be done for deleted objects, and updated to check cascaded mappings. A verifyObject method was added, but it is only used in a couple new tests. - existing tests that insert/update must use verify - need a verifyDelete for delete tests - verify needs to cascade by mapping
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 Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
