Tatu Saloranta

@rafalbednarczuk This is from source calls, but the challenge is how to introspect this for given type: starting point is likely just type-erased `Class` (or with `TypeReference` it'd be super-type...

@rafalbednarczuk It really depends on exactly how it can be implemented, but ideally only in Kotlin module. Core components can not really use kotlin-core in any form (nor features beyond...

@rafalbednarczuk Main problem is just non-scalability (and fragility of sub-classing in general) of this approach: `ObjectMapper` has many methods, but there is also `ObjectReader` (which can not really be easily...

I have no plans to work on this myself, I am offering information that helps others to possibly implement it (and outline some challenges). So if you want to work...

Typically you would fork whatever you want to contribute fix/change for.

Not sure if it'd help but there is separate value `As.EXISTING_PROPERTY` meant to be used when Type Id is not "virtual" property (that is, matches an actual non-metadata Object property)....

Right, you would not want to use `EXTERNAL_PROPERTY`, that has different semantics (it expects property within "parent" (enclosing) JSON Object). But unfortunate that `EXISTING_PROPERTY` makes no difference.

I don't know, was just trying to suggest things to try. I do not know Kotlin module (or Kotlin) well enough so I hope someone else can comment on specific...

Kotlin issue, needs to go under Kotlin module issue tracker; will transfer.

I am not sure this is a bug as there is nothing automatic wrt `@JsonValue` on deserialization: it is not designed to have any effect on deserialization of POJOs... although...