Exclusive updates on:

JSR-310 Announced: Date and Time API

by Rob Thornton on Feb 01, 2007 |

Stephen Colebourne has announced JSR 310, a new Date and Time API, to be based on Joda-Time and hopefully shipping in Java 7. As the JSR reads, the goal is to provide a more advanced and comprehensive model for date and time than those found in the Date and Calendar APIs.

Colebourne is the Project Lead for Joda-Time, and he states that while the JSR will be influenced by Joda-Time, it will not be a rubber stamp of it. Alex Miller lists some of the problems of the current API, from the perspective of working with JDBC drivers.

Colebourne has solicited input in a thread on JavaLobby. Some of the feedback that has already come in includes:

simplifying the API, at least for basic cases
lightweight and high performance (Calendar is slow)
integration with JDBC

The question of compatibility with existing Date and Calendar classes has also come up, with some saying it is necessary and others saying that at the most there should be a helper class for conversions.

Related Editorial

Building Content-Driven Apps - Couchbase and Elasticsearch for Content and Metadata Stores

Making the Shift from Relational to NoSQL

Easy Mobilization for Java EE

Faster PHP Through Java

From Killer Apps to App Killers: The Devastating Effect of Architecturally Complex Defects

Hello stranger!

You need to Register an InfoQ account or to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Community comments

This is welcome by Twice Tshwenyane Posted

Re: This is welcome by Martin Gilday Posted

This is welcome by Twice Tshwenyane

I think this is long overdue. Joda-Time is a very good library and we have suffered for so long at the hands of the JDK Date classes.

Re: This is welcome by Martin Gilday

As long as this includes good JDBC integration this should be a win for everyone. We have used joda-time almost exclusively but having to perform conversions to and from JDBC calls is awkward.