[OPENJPA-1097] Detachment processing of our proxied mutable types (Date, Timestamp, etc) needs to be consistent

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.2.2, 1.3.0, 2.0.0-M1
• Fix Version/s: 1.3.0, 2.0.0-beta3
• Component/s: jpa
• Assignee: Donald Woods
• Reporter: Kevin W. Sutter
• Created: 21/May/09 13:45
• Updated: 05/Apr/10 15:45
• Resolved: 22/Mar/10 19:04

Description

Per the discussion on our forums [1], there seems to some consistent issues with how we perform detachment processing of the mutable types such as Date, Timestamp, etc. There seems to be a couple of issues (at least)...

o Detachment processing is not consistent between the detach() method and the clear() method.
o Tracking of changes on a detached entity, but still allow it to be serialized without requiring the openjpa jar file.

[1] http://n2.nabble.com/Date-Problem-td2943310.html#a2943310

Issue Links

• is related to: OPENJPA-968 Change in default detach() behavior for JPA 2.0
• relates to: OPENJPA-1597 Need Compatibility setting for new OPENJPA-1097 Proxies and DetachedStateField behavior
• relates to: OPENJPA-1571 The change in the element collection is not persisted to the database during merging a detached entity