Community
Participate
Working Groups
In the testsuite eclipselink.jpa.wdf.tests, the test TestBidirectionalManyToMany.testDeleteNonSharedProject fails if caching is enabled (https://bugs.eclipse.org/bugs/attachment.cgi?id=188603). The test checks correct removal behaviour in a bidirectional m:m relationship between the enties Employee and Project. The test removes the association between a Project and an employee and also removes the Project itself. After commit the removed project can still be found: java.lang.AssertionError: project found at org.junit.Assert.fail(Assert.java:91) at org.junit.Assert.assertTrue(Assert.java:43) at org.eclipse.persistence.testing.framework.wdf.AbstractBaseTest.verify(AbstractBaseTest.java:317) at org.eclipse.persistence.testing.tests.wdf.jpa1.relation.TestBidirectionalManyToMany.testDeleteNonSharedProject(TestBidirectionalManyToMany.java:227) The issue does not occur, if the cache is disabled.
see also: bug 336731 and bug 337427
Closing. This test no longer fails when caching is enabled. We have done several fixes to our protected relationship code in 2.3.1 and one of those fixes likely addresses this issue. I have set the cache mode as set in the attachment, run the tests and checked in the change to the persistence.xml file. All tests still pass.
reopening... I missed a change. 'still investigating.
Fix for 336726 fixes this *** This bug has been marked as a duplicate of bug 336726 ***
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink