Bug in JSON Mapping for ZonedDateTime

[hohwille]

It seems as if with #112 I found a bug in jacksons JavaTimeModule:
When a ZonedDateTime is deserialized, then Jackson uses InstantDeserializer when JavaTimeModule is in place. This is indeed producing a ZonedDateTime but the ZoneId is then added as offset and lost resulting in being "1999-12-31T23:59:59+02:00" deserialized as "1999-12-31T21:59:59Z[UTC]".
I traced it down to the root which is here:
https://github.com/FasterXML/jackson-modules-java8/blob/master/datetime/src/main/java/com/fasterxml/jackson/datatype/jsr310/deser/InstantDeserializer.java#L209

Actually one would need to use ZonedDateTime.parse(CharSequence) to properly deserialize ZonedDateTime.

[hohwille]

This test is failing so @Ignore was added:

devon4j/modules/json/src/test/java/com/devonfw/module/json/common/base/type/PageableJsonTest.java

Line 157 in c9a31f5

public void testJavaTimeZonedDateTime() throws Exception {

[hohwille]

We need to configure DeserializationFeature.ADJUST_DATES_TO_CONTEXT_TIME_ZONE.

[hohwille]

Fix needs to go here:
https://github.com/devonfw/devon4j/blob/develop/modules/json/src/main/java/com/devonfw/module/json/common/base/ObjectMapperFactory.java#L154

[hohwille]

Fixed with PR #185 thanks to @vapadwal