This question already has an answer here:
We try to parse the following ISO 8601 DateTime String with timezone offset:
final String input = "2022-03-17T23:00:00.000+0000";
OffsetDateTime.parse(input);
LocalDateTime.parse(input, DateTimeFormatter.ISO_OFFSET_DATE_TIME);
Both approaches fail (which makes sense as OffsetDateTime
also use the DateTimeFormatter.ISO_OFFSET_DATE_TIME
) because of the colon in the timezone offset.
java.time.format.DateTimeParseException: Text '2022-03-17T23:00:00.000+0000' could not be parsed at index 23
But according to Wikipedia there are 4 valid formats for a timezone offset:
<time>Z
<time>±hh:mm
<time>±hhmm
<time>±hh
Other frameworks/languages can parse this string without any issues, e.g. the Javascript Date()
or Jacksons ISO8601Utils
(they discuss this issue here)
Now we could write our own DateTimeFormatter
with a complex RegEx, but in my opinion the java.time
library should be able to parse this valid ISO 8601 string by default as it is a valid one.
For now we use Jacksons ISO8601DateFormat
, but we would prefer to use the official date.time
library to work with. What would be your approach to tackle this issue?
I wouldn't call it a solution but a workaround. SimpleDateFormat's
Z
template supports the timezone-syntax you showed, so you can do something like this:You're still using official libraries shipped with the JVM. One isn't part of the date.time-library, but still ;-)
You don't need to write a complex regex - you can build a
DateTimeFormatter
that will work with that format easily:That will also accept "Z" instead of "0000". It will not accept "+00:00" (with the colon or similar. That's surprising given the documentation, but if your value always has the UTC offset without the colon, it should be okay.
If you want to parse all valid formats of offsets (
Z
,±hh:mm
,±hhmm
and±hh
), one alternative is to use ajava.time.format.DateTimeFormatterBuilder
with optional patterns (unfortunatelly, it seems that there's no single pattern letter to match them all):All the four cases above will parse it to
2022-03-17T23:00Z
.You can also define a single string pattern if you want, using
[]
to delimiter the optional sections:This formatter also works for all cases, just like the previous formatter above. Check the javadoc to get more details about each pattern.
Notes:
.SSS
). On the other hand,ISO_LOCAL_DATE_TIME
is more flexible: the seconds and nanoseconds are optional, and it also accepts from 0 to 9 digits after the decimal point. Choose the one that works best for your input data.Since it is without colon, can you use your own format string :