[
https://issues.apache.org/jira/browse/OFBIZ-3245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781470#action_12781470
]
Adrian Crum commented on OFBIZ-3245:
------------------------------------
David,
I re-read your initial comment and you are correct - this change will affect
things from the API point of view. Actually, that was my original goal.
The Java type specified in the fieldtypes*.xml files must be a Java class that
the JDBC driver recognizes, otherwise an exception will be thrown. Let's say we
want to add a new Java object type to the framework - like the TimeDuration
that I'm trying get implemented. In the existing code, having something like
{code}
<field-type-def type="duration" sql-type="NUMERIC(20,0)"
java-type="TimeDuration"></field-type-def>
{code}
won't work because the JDBC driver doesn't know what to do with a TimeDuration
Java object type. Like you said, the TimeDuration object is passed to the JDBC
driver as-is, and the result is it blows up.
So, this change will make the entity engine more flexible, more adaptable.
Users will be able to introduce their own data types without having to change
entity engine Java code.
> Sandbox: Integrating The New Conversion Framework Into The Entity Engine
> ------------------------------------------------------------------------
>
> Key: OFBIZ-3245
> URL: https://issues.apache.org/jira/browse/OFBIZ-3245
> Project: OFBiz
> Issue Type: Improvement
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Adrian Crum
> Assignee: Adrian Crum
> Priority: Minor
> Attachments: conversion.patch, conversion.patch
>
>
> This issue contains a patch intended for evaluation before it is committed.
> See comments for details.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
