JsonSetter.contentNulls is ignored if the deserialization result from a token that is not JsonToken.VALUE_NULL is null.

[k163377]

Search before asking

• I searched in the issues and found nothing similar.

Describe the bug

This is a follow-up to the following issues
#5139 (fixed via PR #5140)
FasterXML/jackson-module-kotlin#976

In the deserializer inheriting from ContainerDeserializerBase, I found problems in the following classes

• EnumMapDeserializer
• MapDeserializer
• ObjectArrayDeserializer
• StringCollectionDeserializer

The StringArrayDeserializer does not inherit from the ContainerDeserializerBase, but seems to have the same problem.
There may be other deserializers with similar problems, but I have not been able to verify them.

The MapEntryDeserializer was not using _nullProvider.
However, it has not been confirmed that there is no problem with not using _nullProvider.

Version Information

2.19.0(2.19.1-SNAPSHOT)

Reproduction

Same as #5139

Expected behavior

If the deserialization result of the value is null, then JsonSetter.contentNulls must work.

Additional context

No response

[JooHyukKim]

Is there reproduction u can share? If its difficult to convert to Java, even maybe in Kotlin version would be good starting point

[k163377]

For MapDeserializer, it is easy to reproduce since the conversion from empty string to Integer returns null(see this).
The ObjectArrayDeserializer may be reproduced in the same way.

As for the others, I don't think they can be reproduced without defining a custom deserializer that returns null for the value.

If you need all the reproducible cases, please give me some time to create them.
I have a few things to do today, so all submissions will probably be due at the end of next week.

[cowtowncoder]

I think creating one test, listing other likely types, is fine. Test PR can be against 2.19; can then see where fixes should go (2.19 or 2.x depending on how big/risky changes are).

[k163377]

A PR has been issued to add a failing test.
#5174

The EnumSetDeserializer was not reported initially, but a case was added because of a similar problem.