用leap秒来解析持续时间，例如00:00:60

Question

How can I parse a time duration with leap second to seconds?

Example, we are receiving from another service the following duration 00:00:60 which means 1 minute but Java 8 DateTimeFormatter.ofPattern("HH:mm:ss[.SSS]") throws

java.time.format.DateTimeParseException: Text '00:00:60' could not be parsed: Invalid value for SecondOfMinute (valid values 0 - 59): 60

Which makes sense because there is no notion of 60 seconds in the ISO standard used by Java.

I would like to avoid using String::replace (as suggested in other SO answers to similar case) and the use of external library if possible.

This is the current code that is throwing the exception:

private static final DateTimeFormatter TIME_FORMATTER = DateTimeFormatter.ofPattern("HH:mm:ss[.SSS]");

public static Integer parseToSeconds(String durationText) {

    return LocalTime.parse(durationText, TIME_FORMATTER).toSecondOfDay();
}

Answer 1

This is how I solved the issue:

private static final DateTimeFormatter TIME_FORMATTER = DateTimeFormatter.ofPattern("HH:mm:ss[.SSS]");

public static long parsesToSeconds(String durationText) {
    Duration timeSum = Duration.ZERO;
    // Reformat to ISO 8601
    durationText = durationText.replaceFirst("(\\d{2}):(\\d{2}):(\\d{2}(?:\\.\\d+)?)", "PT$1H$2M$3S");

    timeSum = timeSum.plus(Duration.parse(durationText));

    return timeSum.getSeconds();
}

Credits to Ole VV with his answer here: https://stackoverflow.com/a/52315938/2240409

Answer 2

This is what we have lenient resolver style for.

    String durationText = "00:00:60";
    DateTimeFormatter lenientTimeFormatter = DateTimeFormatter.ISO_LOCAL_TIME
            .withResolverStyle(ResolverStyle.LENIENT);
    int seconds = LocalTime.parse(durationText, lenientTimeFormatter).toSecondOfDay();
    System.out.println(seconds);

The output from this snippet is:

60

If your 60 seconds are really a duration, not a time of day, I don't really like it. Then I'd rather parse into a Duration as you do in your own answer. I know that String.replace with a hard-to-read regular expression isn't a very good solution either, but I still think I'd prefer it over pretending that a duration is a time of day if this is downright wrong. I just thought I'd present the option anyway and let you make your own pick based on your reality and preferences.