[
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14547072#comment-14547072
]
Andy Jefferson commented on JDO-709:
------------------------------------
XML schema updates now in SVN.
Something that would make the annotation route much better for handling
embedded fields is to be able to specify the converter in @Persistent,
@Element, @Key, @Value (so we can get rid of the "name" attribute from @Convert
- seems this was copied from JPA where they have no concept of key or value
metadata). The problem with this is the crapness of Java annotation defaulting,
where we can't have a default of null. That is, it would be nice to add this to
@Persistent etc
Class<? extends AttributeConverter> converter() default null;
we can't do that, and we can't use "void.class" either due to the generics
usage on the Class.
My suggestion is that we create an arbitrary NullAttributeConverter class that
is then specified as the default (and an implementation can check for that and
ignore it if so). Opinions?
> 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-xml-2.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)
