[
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343641#comment-17343641
]
Craig L Russell commented on JDO-709:
-------------------------------------
[~andyj]
> A "converted class" doesn't track changes *unless* the provider happens to
> have a wrapper class for that type. There is no obligation on a JDO provider
> to provide a wrapper for all possible types that a user may want to convert.
I agree with this. I've removed the wording that proposed to treat converted
fields as if they were fields of mutable system types.
> Standardize field/property converters
> -------------------------------------
>
> Key: JDO-709
> URL: https://issues.apache.org/jira/browse/JDO-709
> Project: JDO
> Issue Type: New Feature
> Components: api, specification, tck
> Reporter: Matthew T. Adams
> Assignee: Craig L Russell
> Priority: Minor
> Labels: converstion, converter, jdo, type, type-converter
> Fix For: JDO 3.2
>
> Attachments: JDO-709-01.patch, JDO-709-3.patch, JDO-709-4.patch
>
>
> This request is to standardize a user's ability to specify conversions of
> fields or properties of persistence-capable classes. Currently, this is left
> to vendor extensions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
