ISO8601DateFormat is deprecated but replacement is unclear.

com.fasterxml.jackson.databind.util.ISO8601DateFormat is deprecated since 2.9 but I couldn’t find any information about how to replace its current usage while upgrading.

So far, I checked the following locations:

• the release notes.
• the related blog entry.
• the related issue.
• StackOverflow

But no luck…

I suspect that I could probably just delete objectMapper.setDateFormat(new ISO8601DateFormat()); and be fine but I wanted to double-check.

So this is a bug report against the documentation, not the code. If it can be safely removed and dates are still serialized as ISO-8601 strings then this should be mentioned somewhere.

[dmitrygusev]

Looks like default StdDateFormat doesn’t format date-time the same as ISO8601DateFormat.

I found this while integrating with a 3rd party API which uses Swagger spec. In Swagger they have a date-time data type:

date-time – the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z

According to the RFC the timezone information must follow this BNF:

   time-numoffset  = ("+" / "-") time-hour ":" time-minute
   time-offset     = "Z" / time-numoffset
...
   full-time       = partial-time time-offset

Notice the ":" in time-numoffset is not optional, but default StdDateFormat is omitting it, so Swagger implementations will refuse such dates.

Not sure if that’s an issue in RFC or Swagger, but I cannot really use the default StdDateFormat. With ISO8601DateFormat everything works as expected, but as I understand the class is deprecated for removal.

[rferreira]

For posterity, here’s an example of serializing to iso8601 without the ISO8601DateFormat class from the jackson tests themselves: https://github.com/FasterXML/jackson-databind/blob/b1aa8e300519076b2140a2bfd73bf0eac73191de/src/test/java/com/fasterxml/jackson/databind/ser/jdk/DateSerializationTest.java#L118