Tatu Saloranta

I suspect this is working in unexpected way, not because child package handling didn't work, but because of the way base type is determined during serialization. This is an unfortunate...

Ah. The issue that I think you hit is #1358. In the meantime, to anchor base type on write, you might be able to use (... if you didn't use...

I linked to #1358 bit too quickly, without checking. It might not be the issue I was thinking for. Problem I am thinking of is definitely not specific to `defaultImpl`....

@JooHyukKim Problem is that computing of "minimal" type id uses different information during serialization and deserialization, for root values (issue not affecting non-root values): 1. On deserialization polymorphic base type...

@blacelle I am open to different ideas, but in general `AnnotationIntrospector` is not meant to do things more complicated than accessing annotations in flattened form. It should not traverse type/object...

Quick note: I don't think I want an auto-formatter, based on negative experiences I've had over time on level of effort to try to get things to work the way...

Thinking about this more, I think `MapperFeature`s probably not needed but rather the abstraction (`JacksonReflectionAccess`), with default implementation and configurability.

This could be a version discrepancy with your set up (older version of `jackson-databind`, pre-2.17)? Method referenced in exception was added in 2.17, I think. So it could be that...

Thank you for sharing @rpkyrych. This makes sense.

At this point, contributions would be against 2.16. Contributions always welcome!