You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Rick Curtis (JIRA)" <ji...@apache.org> on 2013/10/22 22:02:50 UTC
[jira] [Updated] (OPENJPA-2408) CLONE - Merge of lazily fetched
fields, and merge of managed entities deviates from spec
[ https://issues.apache.org/jira/browse/OPENJPA-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis updated OPENJPA-2408:
---------------------------------
Fix Version/s: (was: 2.2.0)
> CLONE - Merge of lazily fetched fields, and merge of managed entities deviates from spec
> ----------------------------------------------------------------------------------------
>
> Key: OPENJPA-2408
> URL: https://issues.apache.org/jira/browse/OPENJPA-2408
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 2.1.0, 2.2.0
> Reporter: Luca Masini
> Assignee: Rick Curtis
>
> Attached is a test case that illustrates this fail (You can place it into openjpa-persistence-jdbc/src/test/java/org.apache.openjpa.persistence.merge)
> Problem 1: Section 3.2.7.1 (Merging Detached Entity State) of the specification says that "The persistence provider must not merge fields marked LAZY that have not been fetched: it must ignore such fields when merging.". The attached test case illustrates that OpenJPA 2.1.0 does not ignore fields marked LAZY that have not been fetched.
> Problem 2: In the same section, the specification says "If X is a managed entity, it is ignored by the merge operation...". But OpenJPA 2.1.0 doesn't seem to ignore them.
--
This message was sent by Atlassian JIRA
(v6.1#6144)