[jira] [Commented] (OPENJPA-1983) Merge of lazily fetched fields, and merge of managed entities deviates from spec

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on OPENJPA-1983:
----------------------------------------------------------

Commit 1504611 from [~jpaheath] in branch 'openjpa/branches/2'
[ https://svn.apache.org/r1504611 ]

OPENJPA-1983: Don't cascade to an unloaded field when merge is called on a managed Entity - back ported Rick Curtis' trunk changes to 2.0.x.
                
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira