Home > Java > Thoughts on JSR-310

Thoughts on JSR-310

The JSR-310 API recently entered early draft review. Will Java get a decent date/time API at last? See for yourself at http://wiki.java.net/bin/view/Projects/DateTimeEDR1. My thoughts are summarized here.

Some parts look promising. The API uses immutable objects, which is good! It provides aptly named methods for all fields, for example getYear, and for arithmetic, for example plusDays and minusHours.

Some parts are a bit complex, though. So is the subject matter, but still. Simple parsing and formatting seem to be a bit involved unless you can use one of the pre-defined formats. Ideally there should be toString and valueOf methods with format strings, simple and easy to work with for the basic cases.

There should be a common interface and comparisons/operations that take mixed types. LocalDate should certainly be comparable with LocalDateTime (pick midnight) and preferably with ZonedDateTime as well (default time zone). Ideally the older types, at least java.util.Date, should be usable as well.

Clock is documented as throwing UnsupportedOperationException for withZone. Why? Assume the (not uncommon) use case where a web application has users from all over the world and matches the active user’s time zone. Naturally it will not use the system time zone. In general I don’t like methods to throw UnsupportedOperationException. If an operation is optional, push it down to a sub-class or use a different interface and make it clear what is available and what is not.

The TimeSource, which seems to be intended for low-level operations, uses milliseconds according to the documentation. It could use nanoseconds instead or as well. Instant itself has nano-second support, so the API in general is fine.

Last but not least, look into performance! Calendar is often a tight spot. Make the common operations, like construction and date arithmetic, run fast.

Categories: Java
  1. Stephen Colebourne
    2010-03-08 at 08:59

    Thanks for the excellent feedback.

    Various people have commented on ease of formatting. We’ll take a look.

    Comparison of different objects is already supported. This will sort by local date:

    List list = …
    list.sort(list, LocalDate.rule());

    The UnsupportedOperationException methods are a necessary evil. It is unlikely that sensible implementations will throw this, but not inconceivable. The supplied implementations don’t throw and are documented as such.

    TimeSource is intended for use if you are only working with machine time, such as a timestamp (never read by a human). It supports nanoseconds internally, but the only JDK time source is System.currentTimeMillis which is millisecond based.

    Performance is checked to some degree, but more tuning will be needed.

    thanks again,
    Stephen Colebourne (spec lead)

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: