openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-2408) CLONE - Merge of lazily fetched fields, and merge of managed entities deviates from spec
Date Fri, 25 Oct 2013 19:38:30 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-2408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805625#comment-13805625
] 

Rick Curtis commented on OPENJPA-2408:
--------------------------------------

[~masini] -- Can I have you post the unit test that you mentioned? Have you tested this behavior
on trunk, or are you only seeing this on 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)

Mime
View raw message