Tatu Saloranta comments

Results 3335 comments of


                                            Tatu Saloranta

Deserialization regression: MismatchedInput No Object Id found for an instance of X to assign to property '@id'

Sounds like a bug indeed. Thank you for reporting this @susanw1 -- and for verifying it is reproducible with JSON (and not only for YAML as originally mentioned).

Deserialization regression: MismatchedInput No Object Id found for an instance of X to assign to property '@id'

I am not sure this is valid usage, actually: why is `@JsonIdentityInfo` being added when no Object Id is to be used? What is the intention here? (could the annotation...

Deserialization regression: MismatchedInput No Object Id found for an instance of X to assign to property '@id'

Ok, I think our reproduction may be wrong then: in case YAML, there is NATIVE Object Id and Type Id, and to make use of Object Ids (native or property-based,...

Deserialization regression: MismatchedInput No Object Id found for an instance of X to assign to property '@id'

Ok so fix to #4610 looks like it is somewhat related, merged now. Although it only affects case of `DeserializationFeature.FAIL_ON_UNRESOLVED_OBJECT_IDS` being disabled (defaults to enabled).

Deserialization regression: MismatchedInput No Object Id found for an instance of X to assign to property '@id'

Hmmmmh. Looking at code in `BeanDeserializer`: ``` if (p.canReadObjectId()) { Object id = p.getObjectId(); if (id != null) { _handleTypedObjectId(p, ctxt, bean, id); } } // [databind#3838]: since 2.16 Uniform...

Deserialization regression: MismatchedInput No Object Id found for an instance of X to assign to property '@id'

Interestingly enough, that change would solve 1 of 2 failing cases for reproduction @susanw1 provided. Ahh. It fixes YAML case, but fails JSON case... which I think is true. @susanw1...

Deserialization regression: MismatchedInput No Object Id found for an instance of X to assign to property '@id'

Considered fixed via #4612 to be released in 2.17.2 (and 2.18.0)

Provide a way to get bound keys

I don't really see the feature as suggested feasible or generally useful (also rather difficult if not impossible to implement but that aside). So basically "what @pjfanning said". Will leave...

The `KeyDeserializer` specified in the class with `@JsonDeserialize(keyUsing = ...)` is overwritten by the `KeyDeserializer` specified in the `ObjectMapper`.

Sounds like a bug indeed.

The `KeyDeserializer` specified in the class with `@JsonDeserialize(keyUsing = ...)` is overwritten by the `KeyDeserializer` specified in the `ObjectMapper`.

Thank you @k163377 -- I think fix is correct & clean, will proceed with it!