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

Bug 315062

Summary: Better exception information for "a relationship that was not marked cascade PERSIST"
Product: z_Archived Reporter: Tom Eugelink <tbee>
Component: EclipselinkAssignee: Nobody - feel free to take it <nobody>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3    
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Tom Eugelink CLA 2010-05-31 07:34:21 EDT 
Build Identifier: 2.0.2

The solving of the exception "During synchronization a new object was found through a relationship that was not marked cascade PERSIST" can be very complex; which relation is causing the entity to be included? It was removed from it's primary master-detail, but apparently some other is still triggering this.

Would it be possible to not only specify which entity is suppose to be persisted, but also via which path this is decided?

Reproducible: Always
Comment 1 Eclipse Webmaster CLA 2022-06-09 10:32:34 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink