Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
StdDateFormat: add option to serialize timezone offset with a colon
See original GitHub issueJackson’s StdDateFormat serializes datetimes without colon in the timezone offset, eg. 1970-01-01T01:00:00.123+0100.
Java8 and Joda have decided to include a colon in the offset, eg 1970-01-01T01:00:00.123+01:00.
Although Joda accepts to deserialize a datetime with or without the colon, Java8 considers the colon as mandatory and fails to deserialize datetimes produced Jackson’s StdDateFormat.
In addition, some platforms like iOS also require a colon in the offset and are therefore also unable to read dates produces by Jackson’s StdDateFormat.
Consequence: It would be nice if Jackson’s StdDateFormat could be easily configured, extended or customized to include a colon in the timezone offset.
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
spring.jackson.date-format=yyyy-MM-dd'T'HH:mm:ss.SSSXXXThe triple X means to use colon per SimpleDateFormat docs from Oracle. https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html?is-external=true@caeaugusto no problem; and I am sorry to hear in a way it is JDK issue… since it is not something we can easily address at this point. But if you or anyone else finds workarounds, links to documentation, maybe even reported bugs in oracle’s bug tracker, those would be good additions here.