[
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549726#comment-14549726
]
Andy Jefferson commented on JDO-709:
------------------------------------
As said above, you cannot do "default null" (my comment "crapness of Java
annotation defaulting"). Maybe get those Java language spec people at Oracle to
allow it?
If you specify "converter" and "disableConversion" then the disable is ignored.
It means the exact same as the XML variant that was already discussed. i.e
1. No converter, no disable -> use PMF converter if one is provided
2. No converter, with disable -> use no converter
3. Converter specified -> use converter
"PMF level" means the same as your "PMF converter"
> 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)
