Description Brian Vetter 2007-02-28 16:14:25 EST

My elements of type date and datetime are currently mapping to varchar(255) instead of date or datetime in the database. The following XSD element

    <element name="lastReboot" type="dateTime"></element>


maps to the following hbm:

<property name="lastReboot" lazy="false" insert="true" update="true" not-null="false" unique="false">
    <column not-null="false" unique="false" name="`lastreboot`"/>
    <type name="org.eclipse.emf.teneo.hibernate.mapping.DefaultToStringUserType">
        <param name="edatatype">Date</param>
        <param name="epackage">http://www.eclipse.org/emf/2003/XMLType</param>
    </type>
</property>

The ecore mapping looks like:
   <eStructuralFeatures xsi:type="ecore:EAttribute" name="lastReboot" unique="false"
       eType="ecore:EDataType http://www.eclipse.org/emf/2003/XMLType#//DateTime">
     <eAnnotations source="http:///org/eclipse/emf/ecore/util/ExtendedMetaData">
       <details key="kind" value="element"/>
       <details key="name" value="lastReboot"/>
       <details key="namespace" value="##targetNamespace"/>
     </eAnnotations>
   </eStructuralFeatures>

Although it looks like the DateTime type is preserved in the mapping, I noticed that the ecore-Java instanceClass for the eDataType is of type "Object". Teneo always maps this to a String.

Underneath, EMF maintains the date through a class called org.eclipse.xsd.impl.type.XSDDateTimeType whose value is an instance of an internal XMLCalendar class. 

I've created a patch to Teneo's hibernate mapping to fix this. I have not done anything with the JPOX/JDO implementation but I suspect it could have similar issues.