Tatu Saloranta

Note: while parameter names module is required for this occur (to have Constructor parameter names available), handling is in `jackson-databind`: I will transfer the issue.

Inherently ambiguous case; need to use annotations (or `ConstructorDetector`) as mentioned. Closing.

I think what would help here is a simple demonstration of what you mean wrt round-trip consistency. But as to work-around, there is the global default setting, not just per-type:...

@bwaldvogel at this point a specific reproducible unit test would be needed to ensure I actually know the specific failure mode. Textual description is useful but not sufficient. This because...

@bwaldvogel Unfortunately I haven't had time to look into this issue, and probably will not for near future.

This is the way things work unfortunately: there is no merging of dis-joint sequences of elements. It is unlikely to be resolved in near future. But there is a work-around:...

Ok best of luck!

Quick note: correct, `PolymorphicTypeValidator` does not use `@JsonSubTypes` information for anything: `@JsonSubTypes` only helps find Type names used with `@JsonTypeInfo(use = JsonTypeInfo.Id.NAME)` usage. (wherein `Id.CLASS_NAME` does not need such help)....

Although I can see the usefulness of such a setting, I am not sure of a way to expose that in general manner. But maybe this is something that can...

Still no specific feature to use (none of added, `EnumFeature`, `DateTimeFeature`, `JsonNodeFeature` applicable), unfortunately. And having more than 2 states prevents use of `SerializationFeature`. Could change `BigDecimal` serializer to allow...