You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to problems with trying to override builder factory for ObjectMapper, and introduction of JSON-specific format features (JsonReadFeature, JsonWriteFeature), it is necessary to introduce separate JsonMapper, to be used instead of ObjectMapper.
With this (and related Smile, CBOR additions), there will now be format-specific mapper subtype for all formats. ObjectMapper will still exist, and may even be instantiated (more so with 2.10, less with 3.x), but usage should move over to specific mappers for 3.x.
The text was updated successfully, but these errors were encountered:
This is more speaking than using the generic ObjectMapper here, also see
FasterXML/jackson-databind#2153.
Signed-off-by: Sebastian Schuberth <sebastian.schuberth@bosch-si.com>
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Oct 2, 2019
This is more speaking than using the generic ObjectMapper here, also see
FasterXML/jackson-databind#2153.
Signed-off-by: Sebastian Schuberth <sebastian.schuberth@bosch-si.com>
sschuberth
added a commit
to oss-review-toolkit/ort
that referenced
this issue
Oct 7, 2019
This is more speaking than using the generic ObjectMapper here, also see
FasterXML/jackson-databind#2153.
Signed-off-by: Sebastian Schuberth <sebastian.schuberth@bosch-si.com>
Due to problems with trying to override builder factory for
ObjectMapper
, and introduction of JSON-specific format features (JsonReadFeature
,JsonWriteFeature
), it is necessary to introduce separateJsonMapper
, to be used instead ofObjectMapper
.With this (and related Smile, CBOR additions), there will now be format-specific mapper subtype for all formats.
ObjectMapper
will still exist, and may even be instantiated (more so with 2.10, less with 3.x), but usage should move over to specific mappers for 3.x.The text was updated successfully, but these errors were encountered: