Home/ Questions/Q 6566693
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-25T14:14:48+00:00

I have a custom formatter… // default our time zone to the machine local

  • 0

I have a custom formatter…

// default our time zone to the machine local one.
private static final DateTimeZone LOCAL_TZ = DateTimeZone.getDefault();

// format of date (i.e., timestamp) is yyyy-MM-dd HH:mm:ss.S
private static final DateTimeFormatter YEAR_MONTH_DAY_HOUR_MINUTE_SECOND_MILLIS_FORMATTER =
        new DateTimeFormatterBuilder()
.appendYear(4,4)
.appendLiteral('-')
.appendMonthOfYear(1)
.appendLiteral('-')
.appendDayOfMonth(1)
.appendLiteral(' ')
.appendHourOfDay(2)
.appendLiteral(':')
.appendMinuteOfDay(1)
.appendLiteral(':')
.appendSecondOfDay(1)
.appendLiteral('.')
.appendMillisOfDay(1)
.toFormatter().withZone(LOCAL_TZ);

I do something like…

String value = "2011-06-21 05:00:00.0";
YEAR_MONTH_DAY_HOUR_MINUTE_SECOND_MILLIS_FORMATTER.parseDateTime(value);

If I look at the org.joda.time.DateTime in a debugger, I will see that the hour:minute:second.millis got converted to 00:00:00.0.

What gives? I’ve tried mucking around with minDigits on HourOfDay, MinuteOfDay, SecondOfDay and so on. Is this a bug in JodaTime 2.0? Or (more likely) my own ignorance?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You’ve said that it’s 0 millis of the day. In other words, it’s the first millisecond of the day. That obviously conflicts with it being hour 5, and it looks like the last-specified value is taking precedence.

    I suspect you want appendMillisOfSecond – the milliseconds within the already-specified second.

    (Let me know if the difference isn’t clear to you. I’ve recently been writing the parsers and formatters for Noda Time, so I’m coming from a somewhat different perspective to most people…)

    • 0