[
https://issues.apache.org/jira/browse/OPENJPA-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486149#comment-13486149
]
Rick Curtis commented on OPENJPA-2287:
--------------------------------------
I haven't been able to quite figure this one out, but it looks like there is a
bug between the runtime flush logic and the InverseManager trying to 'fix-up'
relationships. As a work around, you could manage your own relationships rather
than relying on the runtime to do it for you?
ie: Remove <property name="openjpa.InverseManager" value="true" /> from your
p.xml file.
> OpenJPA makes fields null
> -------------------------
>
> Key: OPENJPA-2287
> URL: https://issues.apache.org/jira/browse/OPENJPA-2287
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 2.2.0
> Reporter: Maciej Laskowski
> Priority: Critical
>
> When there are two objects in OneToMany relation and when One sets Many and
> vice versa the filed Many.one became null. It seems to be related with code
> added in this issue https://issues.apache.org/jira/browse/OPENJPA-2006. To
> reproduce: https://github.com/dogenkigen/OpenJPA-bug
--
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
