InstantDeserializer shouldAdjustToContextTimezone still references enum entries of DeserializationFeature.ADJUST_DATES_TO_CONTEXT_TIME_ZONE

[marclagula]

Good day!

We are currently in the process of migrating our service from spring-boot 3.5.10 to 4.0.0 and we are currently running into this 1 issue during JSON parsing of datetime fields while running our unit tests:

java.lang.NoSuchFieldError: Class tools.jackson.databind.DeserializationFeature does not have member field 'tools.jackson.databind.DeserializationFeature ADJUST_DATES_TO_CONTEXT_TIME_ZONE'
    at tools.jackson.datatype.jsr310.deser.InstantDeserializer.shouldAdjustToContextTimezone(InstantDeserializer.java:344)
	at tools.jackson.datatype.jsr310.deser.InstantDeserializer._fromString(InstantDeserializer.java:424)
	at tools.jackson.datatype.jsr310.deser.InstantDeserializer.deserialize(InstantDeserializer.java:325)
	...

We tried to disable this during JsonMapper configuration but to no avail:

public static ObjectMapper constructObjectMapper() {
        return JsonMapper.builder()
                .addModule(new JavaTimeModule())
                .changeDefaultPropertyInclusion(incl ->
                        incl.withValueInclusion(JsonInclude.Include.NON_NULL)
                )
                .disable(DateTimeFeature.WRITE_DATES_AS_TIMESTAMPS)
                .disable(DateTimeFeature.ADJUST_DATES_TO_CONTEXT_TIME_ZONE)
                .disable(DeserializationFeature.FAIL_ON_TRAILING_TOKENS)
                .defaultDateFormat(new StdDateFormat())
                .findAndAddModules()
                .build();
    }

Upon looking inside tools.jackson.datatype.jsr310.deser.InstantDeserializer.shouldAdjustToContextTimezone, we noticed that the enum for DeserializationFeature still calls on ADJUST_DATES_TO_CONTEXT_TIME_ZONE, which only exists for Jackson2 but moved to DatetimeFeature for Jackson3. Same is true in shouldReadTimestampsAsNanoseconds method:

    protected boolean shouldAdjustToContextTimezone(DeserializationContext context) {
        return this._adjustToContextTZOverride != null ? this._adjustToContextTZOverride : context.isEnabled(DeserializationFeature.ADJUST_DATES_TO_CONTEXT_TIME_ZONE);
    }

    protected boolean shouldReadTimestampsAsNanoseconds(DeserializationContext context) {
        return this._readTimestampsAsNanosOverride != null ? this._readTimestampsAsNanosOverride : context.isEnabled(DeserializationFeature.READ_DATE_TIMESTAMPS_AS_NANOSECONDS);
    }

We can even see that the value is can no longer be found when navigating to it:

Not sure if this is bug or intended or maybe we're missing something here. Any advise would help.

Thanks!

[marclagula]

To add: We are using the ff version:

<!-- Source: https://mvnrepository.com/artifact/tools.jackson.datatype/jackson-datatype-jsr310 -->
<dependency>
    <groupId>tools.jackson.datatype</groupId>
    <artifactId>jackson-datatype-jsr310</artifactId>
    <version>3.0.0-rc2</version>
    <scope>compile</scope>
</dependency>

[cowtowncoder]

Uh, this:

<version>3.0.0-rc2</version>

is very problematic. Not because it's the second of TEN _pre-release candidates but because this model was ultimately merged into jackson-databind. DO NOT USE IT. Drop it, rely on jackson-databind.

[marclagula]

Updated to use jackson-databind v3.0.4, worked like a charm! Highly appreciate the assistance! Closing this discussion now, will just open a new one should new issues arise

[cowtowncoder]

Great! Best of luck!