[ https://issues.apache.org/jira/browse/OPENJPA-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978407#action_12978407 ]
Rick Curtis commented on OPENJPA-1913: -------------------------------------- @Mark -- I'm pretty sure that we have numerous OpenJPA 'features' that make us non-complaint... as long as your stay to javax.persistence.blah configuration, you'll stay compliant. Once you drop into OpenJPA specific stuff, all bets are off. > 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 > Fix For: 2.2.0 > > 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. - You can reply to this email to add a comment to the issue online.