[
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14516610#comment-14516610
]
Andy Jefferson commented on JDO-709:
------------------------------------
Re: Converter, that was simply to allow some form of defaulting mechanism for
handling fields of a type (from JPA) hence avoiding the need to specify
@Convert on every field of a type. Actually there is nothing in JPA to prevent
the user from (incorrectly) defining multiple (autoApply) @Converter for a
particular java type ... hence a better way of achieving this is desirable, i'm
open to ideas.
Maybe (instead of @Converter) we could have properties you can specify on PMF
startup like "javax.jdo.option.typeconverter.{XXX}" (where XXX is the
fully-qualified type name of the java type) and set this to the
AttributeConverter class name that is the default for that type (and is used if
present in the CLASSPATH and no @Convert is specified against a field of that
type).
> 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
>
>
> 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)
