InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

JSR-310 Announced: Date and Time API

Posted by Rob Thornton on Feb 01, 2007

Sections
Development
Topics
JCP Standards ,
Java
Tags
JSR 310 ,
Joda-Time

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.

This is welcome by Twice Tshwenyane Posted
Re: This is welcome by Martin Gilday Posted
  1. Back to top

    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.

  2. Back to top

    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.

Educational Content

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.

Interview: Software Systems Architecture: Working With Stakeholders Using Viewpoints and Perspectives

InfoQ spoke to the authors of Software Systems Architecture on a couple of new topics, the System Context viewpoint and Agile, which have been added to the second edition.