Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 339043 - Incorrect handling for the type xsd:time
Summary: Incorrect handling for the type xsd:time
Status: RESOLVED FIXED
Alias: None
Product: EMF
Classification: Modeling
Component: Teneo (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Martin Taal CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-06 16:50 EST by Nikita CLA
Modified: 2011-03-17 06:23 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nikita CLA 2011-03-06 16:50:18 EST 
Build Identifier: 1.2.0.v201102272039

If I define a type using XSD with a field of type "xsd:time", mapping this type using Teneo has the following behavior:
 * On MySQL, without any annotations, the resulting JDBC type of the column is Types.DATE.
 * On Oracle, without any annotations, the resulting JDBC type of the column is Types.TIMESTAMP (probably ok?).
 * Using the annotation @Temporal(TemporalType.TIME) results in an exception: java.lang.ClassCastException: org.eclipse.emf.ecore.xml.type.internal.XMLCalendar cannot be cast to java.util.Date

Reproducible: Always

Steps to Reproduce:
Test cases to reproduce the issue are in Assmbla.
Comment 1 Martin Taal CLA 2011-03-17 05:24:28 EDT 
Fix committed to cvs
Comment 2 Martin Taal CLA 2011-03-17 06:23:02 EDT 
Available in latest build