[
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359853#comment-17359853
]
Andy Jefferson commented on JDO-709:
------------------------------------
[~clr] Yes, the "attributeName" was omitted when it was added in 2015; can't
remember why. Easiest option is just to remove "Converts" and move forward, and
maybe add a javadoc comment (to the Convert annotation that an attribute could
be added if wanting to support overriding the specification of converters for
fields of embedded objects) or just add a Jira issue for a future release. But
then I'm not exactly so much in favour of using annotations for such things;
I've never had a need to override a default converter for a field, defined on
the embedded class; the JDO XML definition is way more expressive to achieve
that (IMHO)
> 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)
