[
https://issues.apache.org/jira/browse/OPENJPA-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Albert Lee resolved OPENJPA-1913.
---------------------------------
Resolution: Not A Problem
Fix Version/s: (was: 2.2.0)
Per Jeremy and Rick, this is worked as designed.
> If fetch-groups is used, detaching an entity will lead to all lazy loaded
> members get reset to null
> ---------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1913
> URL: https://issues.apache.org/jira/browse/OPENJPA-1913
> Project: OpenJPA
> Issue Type: Bug
> Components: kernel
> Affects Versions: 2.1.0
> Reporter: Mark Struberg
> Assignee: Jeremy Bauer
> Attachments: OPENJPA-1913-enhancer-fix.patch, OPENJPA-1913-test.patch
>
>
> If I use openjpa.DetachState=fetch-groups and detach an entity with a lazy
> loaded list, this list gets reset to null.
> An example:
> class @Entity Person {
> private String name;
> @OneToMany(mappedBy = "group", cascade = {CascadeType.ALL})
> private List<Subscription> subscriptions = new ArrayList<Subscription>();
> ...}
> I load the Person and access the subscriptions inside a transaction. I get a
> person instance with e.g. 3 subscriptions.
> If I now close the EntityManager and my person gets detached, the
> subscriptions list is suddenly null!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
