[
https://issues.apache.org/jira/browse/OPENJPA-2593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14578582#comment-14578582
]
Alexander Budarov commented on OPENJPA-2593:
--------------------------------------------
Humm, looks I've learnt something new about merge behavior.
After em.merge(), entity can contain obsolete values for fields which were in
detached state.
OpenJPA loads only changed fields from DB in the moment of merge().
em.refresh() works for me (loads fresh state from db).
> Many-to-many collection is not lazily loaded if entity has been merged into
> context right after persist
> -------------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-2593
> URL: https://issues.apache.org/jira/browse/OPENJPA-2593
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Affects Versions: 2.3.0
> Reporter: Alexander Budarov
> Priority: Minor
> Attachments: testcase-mtm.zip
>
>
> Steps are the following:
> 1) Persist an entity which has a many-to-many collection link;
> 2) Create related entity;
> 3) Merge first entity to another persistence context.
> 4) Try to lazily load collection - it does not get loaded.
> If you reload the entity in a separate transaction through
> entityManger.find() before merging - lazy loading works.
> Test project with two test cases attached (please run test methods
> separately).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
