Dropwizard Jackson deserializes offset‑less LocalDateTime as UTC, causing regional time shifts

Recommended approach

Use a custom Jackson module that supplies deserializers for LocalDateTime, ZonedDateTime and OffsetDateTime. When the incoming string lacks an offset/zone, the deserializer applies a configured default ZoneId; otherwise it delegates to the standard JavaTimeModule deserializer. Register this module with Dropwizard’s ObjectMapper via environment.jackson().registerModule(customModule) (or an @Provider returning an ObjectMapper that already contains the module). This avoids the side‑effects of a global setTimeZone call.

Why a global timezone is unsafe

Calling objectMapper.setTimeZone(TimeZone.getTimeZone("America/New_York")) changes the interpretation of every offset‑less date‑time value, including fields that are intentionally meant to stay in UTC (e.g., timestamps annotated with @JsonFormat(shape = STRING, pattern = "yyyy-MM-dd'T'HH:mm:ss'Z'")). Libraries or internal code that expect UTC instants will receive shifted values, leading to subtle bugs.

Steps to implement the custom module

1. Create a class that extends com.fasterxml.jackson.databind.Module (or use SimpleModule).
2. Override the deserializers for the three types:

ZoneId defaultZone = ZoneId.of("America/New_York"); // <-- replace with your desired zone

SimpleModule module = new SimpleModule();
module.addDeserializer(LocalDateTime.class, new JsonDeserializer() {
    @Override
    public LocalDateTime deserialize(JsonParser p, DeserializationContext ctxt) throws IOException {
        String text = p.getText().trim();
        if (text.contains("Z") || text.contains("+") || text.contains("-")) {
            // offset present – delegate to default deserializer
            return p.readValueAs(LocalDateTime.class);
        }
        // no offset – apply default zone and convert to LocalDateTime
        return LocalDateTime.ofInstant(Instant.from(DateTimeFormatter.ISO_OFFSET_DATE_TIME.parse(text + defaultZone.getId())), defaultZone);
    }
});
// Similar overrides for ZonedDateTime and OffsetDateTime, delegating when offset/zone present

3. Register the module after Dropwizard’s defaults:

public void run(MyConfiguration config, Environment environment) {
    environment.jackson().registerModule(module);
    // ... other setup
}

Verification steps

• Send a JSON payload with an offset‑less datetime, e.g., {"eventTime":"2026-10-10T14:30:00"}. Confirm that the resulting LocalDateTime (or ZonedDateTime) equals the instant you obtain by applying your chosen default zone to that string.
• Send a payload with an explicit offset, e.g., {"eventTime":"2026-10-10T14:30:00+05:30"} or "...Z". Verify that the parsed value retains that offset and is not shifted by the default zone.
• Check any existing UTC‑only fields (e.g., annotated with @JsonFormat(shape = STRING, pattern = "yyyy-MM-dd'T'HH:mm:ss'Z'")) to ensure they still deserialize to the same instant as before the module was added.

Missing diagnostic detail

To finalize the recommendation, please specify the ZoneId you wish to use as the default for offset‑less values (e.g., ZoneId.of("America/New_York")).