You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it also applies to zone provided that the zone is a 4 or 6 digit offset.
Either basic or extended formats may be used, but both date and time must use the same format. The date expression may be calendar, week, or ordinal, and must use a complete representation. The time may be represented using a specified reduced accuracy format.[8] It is permitted to omit the 'T' character by mutual agreement.[21]
The text was updated successfully, but these errors were encountered:
challarao
changed the title
Either basic or extended formats may be used, but both date and time must use the same format
ISO8601Utils: Either basic or extended formats may be used, but both date and time must use the same format
Sep 8, 2017
cowtowncoder
changed the title
ISO8601Utils: Either basic or extended formats may be used, but both date and time must use the same formatStdDateFormat: serialize time offset using colon
Sep 13, 2017
Note: this is manifestation of FasterXML/jackson3-dev#7 for Jackson 3.x.
For Jackson 2.x, users need to consider #1744 since we can not safely change defaults (based on past experience, seemingly small defaults changes tend to break some users somewhere).
So: change here is change of StdDateFormat to generate ISO-8601 representation, if no override specified, that does include colon separating hours and minutes in time offset.
I think it also applies to zone provided that the zone is a 4 or 6 digit offset.
https://en.wikipedia.org/wiki/ISO_8601#Combined_date_and_time_representations
The text was updated successfully, but these errors were encountered: