[OPENJPA-1571] The change in the element collection is not persisted to the database during merging a detached entity

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-beta2
• Fix Version/s: 2.0.0-beta3
• Assignee: Donald Woods
• Reporter: Fay Wang
• Created: 15/Mar/10 08:17
• Updated: 29/Mar/10 23:17
• Resolved: 21/Mar/10 00:10

Description

Given an entity:

@Entity
public class EntityB {

@Id
private int id;

@ElementCollection(fetch = FetchType.EAGER)
@CollectionTable(name = "setIntegerTable", joinColumns = @JoinColumn(name = "parent_id"))
@Column(name = "value")
private Set<Integer> intVals;

...
}

The following test scenario

EntityB b1 = em.find(EntityB.class, id);
em.clear();
b1.getIntVals().remove(new Integer(1));
b1.getIntVals().add(new Integer(2));

em.getTransaction().begin();
EntityB b2 = em.merge(b1);
em.getTransaction().commit();
em.clear();

EntityB b3 = em.find(EntityB.class, id);
Set<Integer> intVals = b3.getIntVals();
==> this intVals still only contains Integer(1), not Integer(2).

Issue Links

• is related to: OPENJPA-1097 Detachment processing of our proxied mutable types (Date, Timestamp, etc) needs to be consistent