Tatu Saloranta

I think this may have been fixed for 2.17 (2.17.2) or 2.18 (2.18.0-rc1). Would need a verification: if I have time, I'll try that with given test case.

Ok looking at existing tests, #3133 seems to be the same issue, fixed for 2.15. Will double-check with test but expecting to close this.

Test passes, closing as dup.

First things first: the second case is due to minor bug in `LocationDeserializer` implementation: it does not consume input it needs to: there has to be something like ```java @Override...

Ok so yes, array is included because the internal implementation extracts type id and payload separately (as they are siblings, not wrapped), then combines to look like "as wrapper array"...

`@JsonIgnore` has precedence if both present (as it seems more specific); at any rate, this works as intended. Precedence indeed complicated across annotations: individual annotation types are flattened across hierarchy,...

Problem here is Java Type Erasure, I think. When serializing polymorphic type as root value (direct argument for `writeValue()`), determination of "base type" (base type of polymorphic type hierarchy to...

I'll have to think about this: I do not think `readObject()` works. My initial thinking is/was that we would just have a method for resolving type to create `ObjectReader`; but...

Yes, remove `readObject()`. And test should probably use target types other than `java.lang.Object` (although that can also be used) to ensure actual type introspection -- `Object` is "untyped" target, which...

@rohanlopes20 just realized something: trying to make `ObjectReader readerForAutomatic()` (or similar) probably cannot work as there isn't actual type information included -- `ObjectReader` is not generic (unlike result value for...