You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jdo-dev@db.apache.org by "Andy Jefferson (Jira)" <ji...@apache.org> on 2021/05/10 10:11:00 UTC

[jira] [Commented] (JDO-709) Standardize field/property converters

    [ https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17341813#comment-17341813 ] 

Andy Jefferson commented on JDO-709:
------------------------------------

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.

Fields of a "converted class" are not declared using metadata; the user simply provides a converter that does the conversion for that type.

> 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)