[
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17359994#comment-17359994
]
Andy Jefferson edited comment on JDO-709 at 6/9/21, 11:44 AM:
--------------------------------------------------------------
The other use of the "attributeName" was when wanting to define a converter for
the key/value of a Map (attributeName="key", or attributeName="value"), or when
we have a Collection of some non-persistable element and wanting to define a
converter for the element type. That could be of use, and DataNucleus has the
code for it ... but it *would* require the Converts annotation if the user is
providing "key" *and* "value" converters. So we could add the attributeName to
the Convert annotation just for those 3 specific cases, but ignore the embedded
field converter override. Whether it's worth the effort at this point is
arguable, not so highly used
was (Author: andy):
The other use of the "attributeName" was when wanting to define a converter for
the key/value of a Map (attributeName="key", or attributeName="value"), or when
we have a Collection of some non-persistable element and wanting to define a
converter for the element type. That could be of use, and DataNucleus has the
code for it ... but it does not require the Converts annotation though.
So we could add the attributeName to the Convert annotation just for those 3
specific cases, but ignore the embedded field converter override.
> 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)
