Jackson and JSON in Java, finally learn with a coding-first approach:
>> Download the eBookMocking is an essential part of unit testing, and the Mockito library makes it easy to write clean and intuitive unit tests for your Java code.
Get started with mocking and improve your application tests using our Mockito guide:
Handling concurrency in an application can be a tricky process with many potential pitfalls. A solid grasp of the fundamentals will go a long way to help minimize these issues.
Get started with understanding multi-threaded applications with our Java Concurrency guide:
Spring 5 added support for reactive programming with the Spring WebFlux module, which has been improved upon ever since. Get started with the Reactor project basics and reactive programming in Spring Boot:
Since its introduction in Java 8, the Stream API has become a staple of Java development. The basic operations like iterating, filtering, mapping sequences of elements are deceptively simple to use.
But these can also be overused and fall into some common pitfalls.
To get a better understanding on how Streams work and how to combine them with other language features, check out our guide to Java Streams:
Get started with Spring and Spring Boot, through the Learn Spring course:
>> LEARN SPRINGExplore Spring Boot 3 and Spring 6 in-depth through building a full REST API with the framework:
Yes, Spring Security can be complex, from the more advanced functionality within the Core to the deep OAuth support in the framework.
I built the security material as two full courses - Core and OAuth, to get practical with these more complex scenarios. We explore when and how to use each feature and code through it on the backing project.
You can explore the course here:
Spring Data JPA is a great way to handle the complexity of JPA with the powerful simplicity of Spring Boot.
Get started with Spring Data JPA through the guided reference course:
Refactor Java code safely β and automatically β with OpenRewrite.
Refactoring big codebases by hand is slow, risky, and easy to put off. Thatβs where OpenRewrite comes in. The open-source framework for large-scale, automated code transformations helps teams modernize safely and consistently.
Each month, the creators and maintainers of OpenRewrite at Moderne run live, hands-on training sessions β one for newcomers and one for experienced users. Youβll see how recipes work, how to apply them across projects, and how to modernize code with confidence.
Join the next session, bring your questions, and learn how to automate the kind of work that usually eats your sprint time.
1. Overview
This quick tutorial will illustrate how to use Jackson 2 to deserialize JSON using a custom Deserializer.
To dig deeper into other cool things we can do with Jackson 2, head on over to the main Jackson tutorial.
Further reading:
Intro to the Jackson ObjectMapper
Jackson - Decide What Fields Get Serialized/Deserialized
Jackson - Custom Serializer
2. Standard Deserialization
Letβs start by defining two entities and see how Jackson will deserialize a JSON representation to these entities without any customization:
public class User {
public int id;
public String name;
}
public class Item {
public int id;
public String itemName;
public User owner;
}
Now letβs define the JSON representation we want to deserialize:
{
"id": 1,
"itemName": "theItem",
"owner": {
"id": 2,
"name": "theUser"
}
}
And finally, letβs unmarshal this JSON to Java Entities:
Item itemWithOwner = new ObjectMapper().readValue(json, Item.class);
3. Custom Deserializer on ObjectMapper
In the previous example, the JSON representation matched the Java entities perfectly.
Next, we will simplify the JSON:
{
"id": 1,
"itemName": "theItem",
"createdBy": 2
}
When unmarshalling this to the exact same entities, by default, this will of course fail:
com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException:
Unrecognized field "createdBy" (class org.baeldung.jackson.dtos.Item),
not marked as ignorable (3 known properties: "id", "owner", "itemName"])
at [Source: java.io.StringReader@53c7a917; line: 1, column: 43]
(through reference chain: org.baeldung.jackson.dtos.Item["createdBy"])
Weβll solve this by doing our own deserialization with a custom Deserializer:
public class ItemDeserializer extends StdDeserializer<Item> {
public ItemDeserializer() {
this(null);
}
public ItemDeserializer(Class<?> vc) {
super(vc);
}
@Override
public Item deserialize(JsonParser jp, DeserializationContext ctxt)
throws IOException, JsonProcessingException {
JsonNode node = jp.getCodec().readTree(jp);
int id = (Integer) ((IntNode) node.get("id")).numberValue();
String itemName = node.get("itemName").asText();
int userId = (Integer) ((IntNode) node.get("createdBy")).numberValue();
return new Item(id, itemName, new User(userId, null));
}
}
As we can see, the deserializer is working with the standard Jackson representation of JSON β the JsonNode. Once the input JSON is represented as a JsonNode, we can now extract the relevant information from it and construct our own Item entity.
Simply put, we need to register this custom deserializer and deserialize the JSON normally:
ObjectMapper mapper = new ObjectMapper();
SimpleModule module = new SimpleModule();
module.addDeserializer(Item.class, new ItemDeserializer());
mapper.registerModule(module);
Item readValue = mapper.readValue(json, Item.class);
4. Custom Deserializer on the Class
Alternatively, we can also register the deserializer directly on the class:
@JsonDeserialize(using = ItemDeserializer.class)
public class Item {
...
}
With the deserializer defined at the class level, there is no need to register it on the ObjectMapper β a default mapper will work fine:
Item itemWithOwner = new ObjectMapper().readValue(json, Item.class);
This type of per-class configuration is very useful in situations in which we may not have direct access to the raw ObjectMapper to configure.
5. Custom Deserializer for a Generic Type
Letβs now create a Wrapper class that contains a unique argument of the generic type T:
public class Wrapper<T> {
T value;
public T getValue() {
return value;
}
public void setValue(T value) {
this.value = value;
}
}
The User attribute of our Item will now be of type Wrapper<User> instead:
public class Item {
public int id;
public String itemName;
public Wrapper<User> owner;
}
Letβs implement a custom deserializer for this case.
First, we need to implement the ContextualDeserializer interface to get the entity type inside the Wrapper. Weβll do this by overriding the createContextual() method. When this method is called, the context is resolved, and the actual content of the Wrapper can be retrieved via the BeanProperty argument.
We also have to extend JsonDeserializer. Thus, we can set the concrete type of the Wrapperβs value inside deserialize():
public class WrapperDeserializer extends JsonDeserializer<Wrapper<?>> implements ContextualDeserializer {
private JavaType type;
public WrapperDeserializer() {
// Default constructor
}
private WrapperDeserializer(JavaType type) {
this.type = type;
}
@Override
public JsonDeserializer<?> createContextual(DeserializationContext ctxt, BeanProperty property) {
JavaType wrapperType = property.getType().containedType(0);
return new WrapperDeserializer(wrapperType);
}
@Override
public Wrapper<?> deserialize(JsonParser jsonParser, DeserializationContext deserializationContext) throws IOException {
Wrapper<?> wrapper = new Wrapper<>();
wrapper.setValue(deserializationContext.readValue(jsonParser, type));
return wrapper;
}
}
This JsonDeserializer can also handle multiple Wrapper properties with different types in the same class. Suppose we have a class that contains wrappers with several types:
public class ItemWithMultipleWrappers {
private int id;
private String itemName;
private Wrapper<User> owner;
private Wrapper<Integer> count;
}
In this case, the deserialization would still work because the createContextual() method creates and returns a new instance of WrapperDeserializer with the correct type for each property instead of setting the type field directly.
Finally, we need to register our custom deserializer to be able to deserialize the JSON:
ObjectMapper mapper = new ObjectMapper();
SimpleModule module = new SimpleModule();
module.addDeserializer(Wrapper.class, new WrapperDeserializer());
mapper.registerModule(module);
Item readValue = mapper.readValue(json, Item.class);
6. Conclusion
This article showed how to leverage Jackson 2 to read nonstandard JSON input as well as how to map that input to any Java entity graph with full control over the mapping.
