Change in Json Serialization in resteasy when upgraded Jackson from 2.8.0/2.10.0 to 2.17.2

[mehulparmariitr]

Hello,
I upgraded following libraries after which the JSON output changed. Now I am not getting 0, empty strings.
How to make sure 0 and ""(empty strings) appear in JSON output after serialization of class to make sure my code is backward compatible?

Summary of Upgraded Dependencies

Jackson Core Libraries:
jackson-core upgraded from 2.8.0 to 2.17.2
jackson-databind upgraded from 2.8.0 to 2.17.2
jackson-annotations upgraded from 2.8.0 to 2.17.2

Jackson JAX-RS Provider:
jackson-jaxrs-json-provider upgraded from 2.10.0 to 2.17.2
jackson-jaxrs-base upgraded from 2.10.0 to 2.17.2
jackson-module-jaxb-annotations upgraded from 2.10.0 to 2.17.2

Jackson Module for JSR310 (Java 8 Date and Time API):
jackson-datatype-jsr310 upgraded from 2.8.0 to 2.17.2

Jackson Module for JSON Schema:
jackson-module-jsonSchema upgraded from 2.4.1 to 2.17.2

Swagger JAX-RS:
swagger-jaxrs upgraded from 1.3.12 to 1.6.14

This is my custom JacksonJsonProvider class which is registered in web.xml under resteasy.providers.

import javax.ws.rs.Produces;
import javax.ws.rs.core.MediaType;
import javax.ws.rs.ext.Provider;
import com.fasterxml.jackson.annotation.JsonInclude;
import com.fasterxml.jackson.databind.DeserializationFeature;
import com.fasterxml.jackson.databind.ObjectMapper;
import com.fasterxml.jackson.databind.SerializationFeature;
import com.fasterxml.jackson.jaxrs.json.JacksonJaxbJsonProvider;

@Provider
@Produces(MediaType.APPLICATION_JSON)
public class JacksonJsonProvider extends JacksonJaxbJsonProvider {
    private static ObjectMapper commonMapper = null;
    public JacksonJsonProvider() {
        if (commonMapper == null) {
            ObjectMapper mapper = new ObjectMapper();

            mapper.setSerializationInclusion(JsonInclude.Include.NON_NULL);
            mapper.setSerializationInclusion(JsonInclude.Include.NON_DEFAULT);
            mapper.configure(SerializationFeature.WRITE_DATES_AS_TIMESTAMPS, false);
            mapper.configure(DeserializationFeature.FAIL_ON_UNKNOWN_PROPERTIES, false);

            // Add specific configuration for SEPA authorization
            mapper.registerSubtypes(abc.class);
            commonMapper = mapper;
        }
        super.setMapper(commonMapper);
    }
}

[pjfanning]

This problem is your problem. You have upgraded some ancient versions of libraries including many non-Jackson libs like swagger libs and jersey libs. If you can produce a POC that uses Jackson libs and nothing else, then that suggests a Jackson change causes your issue. You should not expect us to guess without a Jackson only reproduction case.

[mehulparmariitr]

I see its all jackson related libraries only except Swagger. What I want to know is in which Jackson version default behaviour changed for this option? This will help me narrow my search.

mapper.setSerializationInclusion(JsonInclude.Include.NON_DEFAULT);

[mehulparmariitr]

@pjfanning How in previous versions of Jackson (like 2.10.0), setSerializationInclusion(JsonInclude.Include.NON_DEFAULT) was exhibiting this behavior :

• null and 0 were included in the output.
• false and empty arrays ([]) were excluded.

What can be done to make sure in my current libs 2.17.2 this behaviour can be replicated?

[mehulparmariitr]

I tried this config -

mapper.setSerializationInclusion(JsonInclude.Include.NON_NULL);
mapper.setDefaultPropertyInclusion(JsonInclude.Value.construct(JsonInclude.Include.NON_NULL, JsonInclude.Include.NON_EMPTY));

But still I see empty arrays and false boolean values in output

[cowtowncoder]

You'd need to give full stand-alone example, not verbal descriptions of parts of processing.

But handling of NON_DEFAULT for serialization inclusion is problematic due to complex intended semantics.

You may want to search github issues for "NON_DEFAULT" and see what comes up.

[cowtowncoder]

This is an example of way too broad a question -- how did this library change all around between a very big version jump?

A more specific isolated example could be submitted as an issue instead.

If so, reproduction should:

1. Not depend on other frameworks, libraries
2. Contain all necessary classes (in particular value class(es) being serialized)

[mehulparmariitr]

Can you help with this query - #270 (reply in thread)