πŸ“œJackson Module

How to serialize Result objects with Jackson

When using Result objects with Jackson we might run into some problems. The Jackson datatype module for Result solves them by making Jackson treat results as if they were ordinary objects.

Jackson is a Java library for JSON parsing and generation. It is widely used for converting Java objects to JSON and vice versa, making it essential for handling data in web services and RESTful APIs.

How to Use this Add-On

Add this Maven dependency to your build:

Group ID
Artifact ID
Latest Version

com.leakyabstractions

result-jackson

Test Scenario

Let's start by creating a class ApiResponse containing one ordinary and one Result field.

/** Represents an API response */
public class ApiResponse {

  @JsonProperty
  String version;

  @JsonProperty
  Result<String, String> result;

  // Constructors, getters and setters omitted
}

Problem Overview

Then we will take a look at what happens when we try to serialize and deserialize ApiResponse objects.

Serialization Problem

Now, let's instantiate an ApiResponse object.

And finally, let's try serializing it using an object mapper.

We'll see that now we get an InvalidDefinitionException.

While this may look strange, it's the expected behavior. When Jackson examined the result object, it invoked Result::getSuccess and received an optional string value. But Jackson will not handle JDK 8 datatypes like Optional unless you register the appropriate modules.

This is Jackson's default serialization behavior. But we'd like to serialize the result field like this:

Deserialization Problem

Now, let's reverse our previous example, this time trying to deserialize a JSON object into an ApiResponse.

We'll see that we get another InvalidDefinitionException. Let's inspect the stack trace.

This behavior again makes sense. Essentially, Jackson cannot create new result objects because Result is an interface, not a concrete type.

Solution Implementation

What we want, is for Jackson to treat Result values as JSON objects that contain either a success or a failure value. Fortunately, there's a Jackson module that can solve this problem.

Registering the Jackson Datatype Module for Result

Once we have added Result-Jackson as a dependency, all we need to do is register ResultModule with our object mapper.

Alternatively, you can also make Jackson auto-discover the module.

Regardless of the chosen registration mechanism, once the module is registered all functionality is available for all normal Jackson operations.

Serializing Results

Now, let's try and serialize our ApiResponse object again:

If we look at the serialized response, we'll see that this time the result field contains a null failure value and a non-null success value:

Next, we can try serializing a failed result.

We can verify that the serialized response contains a non-null failure value and a null success value.

Deserializing Results

Now, let's repeat our tests for deserialization. If we read our ApiResponse again, we'll see that we no longer get an InvalidDefinitionException.

Finally, let's repeat the test again, this time with a failed result. We'll see that yet again we don't get an exception, and in fact, have a failed result.

Conclusion

We learned how to serialize and deserialize Result objects using Jackson, demonstrating how the provided datatype module enables Jackson to treat Results as ordinary objects.

Last updated

Was this helpful?