Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 315062 - Better exception information for "a relationship that was not marked cascade PERSIST"
Summary: Better exception information for "a relationship that was not marked cascade ...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-31 07:34 EDT by Tom Eugelink CLA
Modified: 2022-06-09 10:32 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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