[
https://issues.apache.org/jira/browse/OPENJPA-1184?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods resolved OPENJPA-1184.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 2.0.0)
(was: 1.2.2)
2.0.0-M3
Patch and tests committed to trunk and 13x. Thanks to David Minor for the
patches.
> Inverse relations not set for MapKey field when using parallel eager select
> ---------------------------------------------------------------------------
>
> Key: OPENJPA-1184
> URL: https://issues.apache.org/jira/browse/OPENJPA-1184
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 1.2.1
> Environment: All environments using JDBC store.
> Reporter: David Minor
> Assignee: Donald Woods
> Fix For: 1.3.0, 2.0.0-M3
>
> Attachments: mapkey-inverse-relation-test.patch, openjpa.patch
>
>
> When selecting multiple entities A which contain a @MapKey field for entity
> B, the inverse relation from B to A will only be set for the first entity A,
> when using parallel eager select. This is because all entity B objects are
> created when loading the 1st entity A object, with the inverse relation to be
> set later in setInverseRelation(), but setInverseRelation() is looking for
> Collection fields only, so the Map fields are ignored.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
