[OPENJPA-2540] merge without DetachedStateField deletes lazy fields in embedded entities

• Type: Bug
• Status: Open
• Priority: Critical
• Resolution: Unresolved
• Affects Version/s: 2.3.0
• Component/s: kernel
• Assignee: Unassigned
• Reporter: Vermeulen
• Created: 24/Oct/14 11:06
• Updated: 27/Oct/14 15:30

Description

I am using the setting <property name="openjpa.DetachState" value="fetch-groups(DetachedStateField=false)" />

Like the summary says, I have an embedded entity with a field that is lazily fetched. This is a field that is persisted whenever the entity is persisted. (It doesn't matter whether it is a @Basic field or a @ManyToOne relation with cascade = CascadeType.ALL). When I merge a detached entity that has null for such a field, the field is actually made null in the database. The expected behavior is for OpenJPA to notice that the field is not in the fetch plan and ignore it on merge.

The problem only exists when using an embedded entity together with the DetachedStateField=false setting.

I created a test case which shows the issue. It is based on that of OPENJPA-1983 which reported a similar issue but whose test case didn't use an embedded entity.

Issue Links

• depends upon: OPENJPA-1983 Merge of lazily fetched fields, and merge of managed entities deviates from spec