You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Andy Jefferson (JIRA)" <ji...@apache.org> on 2015/05/11 16:14:00 UTC
[jira] [Updated] (JDO-709) Standardize field/property converters
[ https://issues.apache.org/jira/browse/JDO-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Jefferson updated JDO-709:
-------------------------------
Attachment: JDO-709-xml-1.patch
Initial patch for updating DTD/XSD. Note only includes jdo.dtd/jdo.xsd since what is in there will be copied to orm.dtd/orm.xsd when accepted.
Current idea is that we have "converter" attribute on <field>, <property>, <key>, <value> and <element> allowing user to specify a converter for the type of that member (or container member). Likely also need an attribute "disable-converter" (true|false) for cases where the PMF has a converter default defined for a java type and in the particular case of some class/field we don't want to use the default.
> 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)