Is there any replacement for deprecated property SerializationFeature.WRITE_NULL_MAP_VALUES in Jackson Databind?
Asked Answered
F

1

9

We are using ObjectMapper to ignore serialisation of null maps in our project

configure(SerializationFeature.WRITE_NULL_MAP_VALUES, false)

But after Jackson-Databind 2.9, the property is depreciated and we are looking for an alternate option.

Can the below code work as substitute for removing the above property -

setSerializationInclusion(Include.NON_NULL)
Fancyfree answered 2/12, 2019 at 9:53 Comment(0)
M
11

From documentation:

Deprecated. Since 2.9 there are better mechanism for specifying filtering; specifically using JsonInclude or configuration overrides (see ObjectMapper.configOverride(Class)). Feature that determines whether Map entries with null values are to be serialized (true) or not (false).
NOTE: unlike other SerializationFeatures, this feature cannot be dynamically changed on per-call basis, because its effect is considered during construction of serializers and property handlers.

Feature is enabled by default.

Simple example:

import com.fasterxml.jackson.annotation.JsonInclude;
import com.fasterxml.jackson.annotation.JsonInclude.Value;
import com.fasterxml.jackson.databind.ObjectMapper;
import com.fasterxml.jackson.databind.SerializationFeature;

import java.util.HashMap;
import java.util.Map;

public class JsonApp {

    public static void main(String[] args) throws Exception {
        Map<String, Object> map = new HashMap<>();
        map.put("string", "value");
        map.put("int", 1);
        map.put("null1", null);
        map.put(null, null);

        ObjectMapper mapper = new ObjectMapper();
        mapper.enable(SerializationFeature.INDENT_OUTPUT);
        mapper.configOverride(Map.class).setInclude(Value.construct(JsonInclude.Include.NON_NULL, JsonInclude.Include.NON_NULL));

        System.out.println(mapper.writeValueAsString(map));
    }
}

Above code prints:

{
  "string" : "value",
  "int" : 1
}
Massotherapy answered 2/12, 2019 at 15:56 Comment(3)
I see that this alteration works, but don't really understand the reason for the deprecation. Can anyone give a more explicit/usefull description for the deprecation?Knocker
Have to admit I also found the javadocs for setInclude rather opaque.Knocker
@BillNaylor, added note should give you better reason why: unlike other SerializationFeatures, this feature cannot be dynamically changed on per-call basis, because its effect is considered during construction of serializers and property handlers.Howarth

© 2022 - 2024 — McMap. All rights reserved.