Bugzilla – Full Text Bug Listing
| Summary: | Add configuration to force MergeManager to fully merge an Entity | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Gordon Yorke <gordon.yorke> | ||||
| Component: | Eclipselink | Assignee: | Nobody - feel free to take it <nobody> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | eclipselink.foundation-inbox | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Code checked in Reviewed by James Sutherland The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink |
Created attachment 194871 [details] Potential Patch For certain configurations where they may not be a cache for maintaining Object Identity the MergeManager should be able to fully merge an Entity and not just use the ChangeSet. This is important when collection are being merged but because there is no object identity being maintained by the cache any removals from the collection will not occur if using a ChangeSet.