Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 336754

Summary: constraint issues with mapped key mappings
Product: z_Archived Reporter: James Sutherland <jamesssss>
Component: EclipselinkAssignee: Project Inbox <eclipselink.orm-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P2 CC: tom.ware
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description James Sutherland CLA 2011-02-09 14:59:16 EST 
If a collection mapping uses a mapped key using a 1-1 or aggregate, it needs to cascade the pre/postInsert/Update/Delete mapping events into the mapping.  Although CollectionMapping seems to do this, most subclasses override these methods and don't seem to do it.

This could lead to constraint issues, or missed writes/delete for aggregate relationships.

Also the new code for handling deletion cycles does not account for mapped keys.  Not sure if our constraint dependencies do either.
Comment 1 Eclipse Webmaster CLA 2022-06-09 10:08:03 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink