The problem I have with jsonConfig.setClassMap is that the keys are not bound to a specific bean class.
As a result this problem could result in an error situation when the same property name is used in a nested bean for different types.
I have already faced this issue several times. Do you agree on this?
Is resolving this issue part of your current roadmap?
Yes, we are aware of this inconvenience, there is already a feature request to take care of this issue.