Java 8's DateTimeFormatter struggles to parse ISO 8601 strings lacking a colon between hours and minutes in the offset, causing difficulties for users attempting to convert strings like "2018-02-13T10:20:12.120 0000" into Java 8 dates.
Until Java 8 Bug Fix:
Until the bug in Java 8 is resolved, use the following workaround:
OffsetDateTime.parse( "2018-02-13T10:20:12.120+0000" , DateTimeFormatter.ofPattern( "uuuu-MM-dd'T'HH:mm:ss.SSSX" ) )
After Java 8 Bug Fix:
OffsetDateTime.parse( "2018-02-13T10:20:12.120+0000" )
Wrong Class Usage
Avoid using legacy classes like Date, Calendar, and SimpleDateFormat in favor of modern java.time classes.
Use OffsetDateTime for Offset-Only Values
For values with offsets but no time zone, use OffsetDateTime. ISO 8601 strings typically comply with the standard formats used by java.time classes. However, a bug in Java 8 requires a workaround:
Hacky Workaround
Manipulate the input string to include the missing colon:
String input = "2018-02-13T10:20:12.120+0000".replace( "+0000" , "+00:00" ); OffsetDateTime odt = OffsetDateTime.parse( input );
More Robust Workaround
Define a DateTimeFormatter with an explicit pattern:
String input = "2018-02-13T10:20:12.120+0000" ; DateTimeFormatter f = DateTimeFormatter.ofPattern( "uuuu-MM-dd'T'HH:mm:ss.SSSX" ); OffsetDateTime odt = OffsetDateTime.parse( input , f );
Additional Considerations
The Java 8 bug affects the parsing of offsets missing the colon between hours and minutes. This issue affects offsets like 0000 but not 00:00.
java.time classes supplant legacy date classes and are built into Java 8 and later. They provide more modern and efficient date-time handling capabilities.
The above is the detailed content of How to Parse ISO 8601 Dates with Missing Colon in Offset in Java 8?. For more information, please follow other related articles on the PHP Chinese website!