Hi Laird,
The line from the spec is here:
"If X is an entity merged to X', with a reference to another entity
Y, where cascade=MERGE
or cascade=ALL is not specified, then navigation of the same
association from X' yields a
reference to a managed object Y' with the same persistent identity
as Y."
The spec asks us to create a Y' and we need a way to do it. I
suspect what other providers do comes down to a combination of how
they have interpreted the spec, and what is tested in the TCK.
Having said that, I think there is an argument that there should
be a way to indicate that an object should not be touched by a merge
and perhaps the lack of CASCADING combined with a read-only setting
would be a good way to determine that. Please feel free to enter an
enhancement request for this behavior.
-Tom
On 06/09/2013 9:41 AM, Laird Nelson
wrote:
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
|