[
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14565341#comment-14565341
]
Craig L Russell commented on JDO-709:
-------------------------------------
I'm having trouble understanding how the implementation can process the
Converters annotation. The value is a list of Convert annotations and the
implementation is supposed to figure out to which domain type the values
(AttributeConverter) apply.
At runtime, I don't think the template types are available, as they have been
erased. How does the implementation figure out the A and D of
AttributeConverter<A, D>? Do we need to add
Class<A> getAttributeClass() and
Class<D> getDatabaseClass()
to the interface requirements of AttributeConverter?
> Standardize field/property converters
> -------------------------------------
>
> Key: JDO-709
> URL: https://issues.apache.org/jira/browse/JDO-709
> Project: JDO
> Issue Type: New Feature
> Components: api
> Reporter: Matthew T. Adams
> Assignee: Matthew T. Adams
> 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
(v6.3.4#6332)
