[
https://issues.apache.org/jira/browse/OPENJPA-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods resolved OPENJPA-1097.
-----------------------------------
Resolution: Fixed
Updated code and docs in 1.3.x and 2.0.0.
Attached patch for 1.2.3 if we ever want to include it there.
> Detachment processing of our proxied mutable types (Date, Timestamp, etc)
> needs to be consistent
> ------------------------------------------------------------------------------------------------
>
> Key: OPENJPA-1097
> URL: https://issues.apache.org/jira/browse/OPENJPA-1097
> Project: OpenJPA
> Issue Type: Bug
> Components: jpa
> Affects Versions: 1.2.2, 1.3.0, 2.0.0-M1
> Reporter: Kevin Sutter
> Assignee: Donald Woods
> Fix For: 1.3.0, 2.0.0
>
> Attachments: OPENJPA-1097-12x-code.patch,
> OPENJPA-1097-12x-tests.diff, OPENJPA-1097-tests.diff,
> OPENJPA-1097-trunk.diff, OPENJPA-1097.1-trunk.patch,
> OPENJPA-1097.2-trunk.patch, OPENJPA-1097.patch, Proxies.java
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
