[
https://issues.apache.org/jira/browse/OPENJPA-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Donald Woods updated OPENJPA-1097:
----------------------------------
Attachment: OPENJPA-1097-tests.diff
some tests showing how detach() and clear() do not unproxy the entities -
160 test INFO [main] Tests - e20.sqlDate =
org.apache.openjpa.util.java$sql$Date$proxy
160 test INFO [main] Tests - e20.sqlTime =
org.apache.openjpa.util.java$sql$Time$proxy
160 test INFO [main] Tests - e20.sqlTimestamp =
org.apache.openjpa.util.java$sql$Timestamp$proxy
but detachCopy() does -
161 test INFO [main] Tests - after detach e20copy
161 test INFO [main] Tests - e20.sqlDate = java.sql.Date
161 test INFO [main] Tests - e20.sqlTime = java.sql.Time
161 test INFO [main] Tests - e20.sqlTimestamp = java.sql.Timestamp
> 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.2.3, 1.3.0, 2.0.0
>
> Attachments: OPENJPA-1097-tests.diff
>
>
> 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.
