Tatu Saloranta

Quick note: not including type information for a small numbef of "natural" types: * String * Boolean * Double * Long is not a bug but feature -- optimization to...

Another note: this may well be due Java "Type Erasure" problem as well -- it is, in general, a bad idea to directly use generic types as root values because...

If anyone has time, would probably make sense to check if this fails with 2.18.0 -- POJO/Record property introspection was rewritten in 2.18 which could help with this case.

If I understand the question, it's whether there is a hook you could register when attempting to serialize a value (instance) of a type. Short answer is "no". But such...

Note on properties- vs delegation-based Creators -- instead of 2 calls, I was also wondering about single call, that could return one (or zero) of each. This because we can...

@pjfanning If it ain't broke don't fix it -- I opened this issue to probe if this could help or not. If not, there is no strict need to do...

We can leave this open for a bit, and if nothing comes out of it, close.

Thank you for reporting this issue. I think I know why it occurs, technically speaking, but not sure how to address it. But in the meantime... to fail on duplicate...

Ideally we should at least give better error message. Good to know of multiple paths that can result in this problem.

Due to implementation I suspect our most practical solution would be just use the first value and ignore the second value (which is different from POJO with setters/fields). This because...