Bug 407093 - Make @Temporal more flexible by only rely on "getTime()" and "setTime()"
Summary: Make @Temporal more flexible by only rely on "getTime()" and "setTime()"
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: All Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Nobody - feel free to take it CLA
QA Contact:
URL:
Whiteboard:
Keywords: investigate, usability
Depends on:
Blocks:
 
Reported: 2013-05-02 13:26 EDT by Hajo Lemcke CLA
Modified: 2022-06-09 10:24 EDT (History)
1 user (show)

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 Hajo Lemcke CLA 2013-05-02 13:26:16 EDT 
To get rid of all the hazzle with date and timezones I would like to use
HalDateTime (see http://sourceforge.net/directory/os:windows/freshness:recently-updated/?q=haldatetime).

Unfortunately @Temporal restricts the underlying class to be either java.util.Date or java.util.Calendar. If this restriction is removed usage would be much easier. At moment we mark the Timestamp column as deprecated and use the getter and setter to update the HalDateTime.
Comment 1 Eclipse Webmaster CLA 2022-06-09 10:24:35 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink