Tatu Saloranta

Yes, I think this is an unfortunate side-effect of `readTree()` having to decide what to do with fractional numbers: whether to read them as 64-bit `double`s (lossy, range), or as...

Or, new (2.19+), `JsonNodeFeature.USE_BIG_DECIMAL_FOR_FLOATS`.

Work-around exists; closing.

@JooHyukKim What do you think about this wrt feasibility/need? You have been working most on any-getter/any-setter support. @alixpeigue Yes, should be free: if someone was working on it, they'd be...

@JooHyukKim I think use of `@JsonAnySetter` for properties for which there is no Field or Setter (hence, "unmapped") is pretty much the main use case?

Would this be same as #2957?

Closing as duplicate of #2957.

Version?

Unfortunately we would really need a stand-alone reproduction here. Could be something simple, but can only investigate when problem occurs (regular test suite passes etc).

Ok. Yes, sometimes that's how things are. There may be something with configuration that matters; perhaps a custom `BeanSerializerModifier` replaces initial `List` of `BeanPropertyDefinition`s with an immutable version, for example.