[
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681744#comment-17681744
]
Tilmann Zäschke commented on JDO-709:
-------------------------------------
To keep this thread somewhat up to date, there have been three PRs/tickets
concerning @Convert on types:
* PR by original problem reporter:
[https://github.com/apache/db-jdo/pull/60|https://github.com/apache/db-jdo/pull/60]
* Copy or original PR with additional TCK test:
[https://github.com/apache/db-jdo/pull/61|https://github.com/apache/db-jdo/pull/61]
* Tickets with problem description on reference implementation:
[https://github.com/datanucleus/datanucleus-api-jdo/issues/127|https://github.com/datanucleus/datanucleus-api-jdo/issues/127]
> 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.20.10#820010)
