[
https://issues.apache.org/jira/browse/OPENJPA-2405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13695690#comment-13695690
]
Mark Struberg commented on OPENJPA-2405:
----------------------------------------
Jody, I'm not sure if the Entity of such a unsynchronized CMTS EM would be
'detached'. At least according to what I talked with Mike Keith (assuming that
I didn't misunderstand him) lazy loading and graph traversal would work for
such entitites.
I agree with your 2nd part. Having the same db row managed in 2 different EMs
will either not see each other properly or if they do (update case) most likely
cause an OptimisticLockingException in one of them - at least if both write!
> EntityManager.merge does not work for entity that is managed by another
> EntityManager
> -------------------------------------------------------------------------------------
>
> Key: OPENJPA-2405
> URL: https://issues.apache.org/jira/browse/OPENJPA-2405
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.2.3
> Reporter: Arne Limburg
> Attachments: OPENJPA-2405.patch
>
>
> EntityManager.merge does not work for entity that is managed by another
> EntityManager. Instead of updating that entity OpenJPA tries to persist the
> entity a second time
--
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
