Tatu Saloranta

@denizhusaj Could you file a separate issue for `ObjectNode.toString()` please? That sounds like a side issue that sounds worth addressing. As to plans: yes, there is a plan but it'd...

If I understand your description correctly, yes, this is how things work and are designed to work. Merging does mean that an existing Object will be updated, and since no...

@cmolodo No problem at all -- I can see how one could think setter would still be involved. I just hadn't even thought of that myself. As to why not...

I would need to have a full reproduction: stack trace itself is unfortunately not enough to tell what is going on (for example: is serialization producing incorrect value -- it...

Hmmh. I will have to think hard for what would be the expected behavior. I can see why you would expect override to work here, but unfortunately due to handling...

@pdegoeje Yes, documentation improvement would be a good idea.

@james-woods That is odd -- defining method `getNullValue(DeserializationContext ctxt)` on custom `String` deserializer should work and there should be no need to override container deserializer. But this handling is distinct...

@pdegoeje Actually, I am not quite sure what is being attempted here. If `Bar` says it (and its subtypes, which is implied by Jackson) are to be handled using polymorphic...

Added a failing test case that shows that override of `@JsonTypeInfo` with `Id.NONE` does not work as expected. Can extend to handling of custom deserializer too, but I wanted to...

Very cool, thank you for sharing more context. I agree that ability to use databinding for most things is good and streaming is much more work. So I hope I...