Community
Participate
Working Groups
Currently Cascade Remove support does not perform shallow updates to break cycles. During the remove cascading process FK's should be updated to break cycles.
Setting target and priority. See the following page for details of what these fields mean: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines
Deferring to 2.2.0, as we are closing down 2.1.1.
I have an issue with this too: class A { A parent; List children (cascade=ALL) } Now I want to remove a part of the tree. As far as I understand the order of the delete statements is essential in order not to violate the constraints. em.remove(a); (a has children) does not work because it violates the FK-constraint - this is because EclipseLink seems to delete the parent first.
Deferring. This fix will not make 2.2.
See Bug 330580 - Support class-level cycles for CascadeRemove for addtional functionality that should be considered when addressing this bug.
Fixed as part of, https://bugs.eclipse.org/bugs/show_bug.cgi?id=328040
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink