[
https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14545795#comment-14545795
]
Craig L Russell commented on JDO-709:
-------------------------------------
Three cases to consider for disable converter:
1. Use a specific converter not the default. This is easy. Specify a Convert
annotation that overrides the default.
2. Don't use the pmf converter for an element. Use the standard converter. Here
we need a "disable pmf converter" on the element.
3. Don't use the pmf converters for any elements in a class or interface. Here
we need a "disable pmf converter" on the class or interface. Any elements that
cannot use the default converter need to have a specific converter on the
element. For example, if there is a converter that converts database strings to
dates, if all pmf converters are disabled on a class, the field needs to have
its own converter specified.
> 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-1.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)
