[
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358226#comment-17358226
]
Craig L Russell commented on JDO-709:
-------------------------------------
[~andyj] When we reviewed the metadata and annotations we found that the JDO
Convert annotation differs from the JPA Convert annotation. JPA has the
attribute name that is not needed if the annotation applies to a field but
would be needed if the annotation applies to a class. If annotating a class,
multiple Convert annotations can be used, and the attribute name is needed to
tell which field is being annotated.
The JDO Convert annotation doesn't have the attribute name, but it does have
the multiple Converts annotation that applies to a persistent class. So it is
inconsistent.
To fix the inconsistency we can either remove the Converts annotation and
remove the Convert applying to a class; or add the attribute name to the
Convert annotation. If we add the attribute name we should probably add a test
case with Converts and multiple Convert applying to multiple attributes.
> 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)
