Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@openjpa.apache.org
Date: Wed, 20 Apr 2011 13:13:05 +0000 (UTC)
From: "Rick Curtis (JIRA)" <jira@apache.org>
To: dev@openjpa.apache.org
Message-ID: 
 <1270868816.69834.1303305185683.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <836803449.67999.1303242725700.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (OPENJPA-1983) Merge of lazily fetched fields, and
 merge of managed entities deviates from spec
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/OPENJPA-1983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rick Curtis updated OPENJPA-1983:
---------------------------------

    Affects Version/s: 2.2.0
        Fix Version/s: 2.2.0

> Merge of lazily fetched fields, and merge of managed entities deviates from spec
> --------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1983
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1983
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 2.1.0, 2.2.0
>            Reporter: Pradyumna Achar
>            Assignee: Rick Curtis
>             Fix For: 2.2.0
>
>         Attachments: Inner.java, OPENJPA-1983.patch, Outer.java, TestLazyFields.java
>
>
> 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 is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira