Is Jackson’s @JsonSubTypes still necessary for polymorphic deserialization?

by

There are two ways to achieve polymorphism in serialization and deserialization with Jackson. They are defined in Section 1. Usage in the link you posted.

Your code

@JsonTypeInfo(
    use = JsonTypeInfo.Id.MINIMAL_CLASS,
    include = JsonTypeInfo.As.PROPERTY,
    property = "@class")

is an example of the second approach. The first thing to note is that

All instances of annotated type and its subtypes use these settings
(unless overridden by another annotation)

So this config value propagates to all subtypes. Then, we need a type identifier that will map a Java type to a text value in the JSON string and vice versa. In your example, this is given by JsonTypeInfo.Id#MINIMAL_CLASS

Means that Java class name with minimal path is used as the type identifier.

So a minimal class name is generated from the target instance and written to the JSON content when serializing. Or a minimal class name is used to determine the target type for deserializing.

You could have also used JsonTypeInfo.Id#NAME which

Means that logical type name is used as type information; name will
then need to be separately resolved to actual concrete type (Class).

To provide such a logical type name, you use @JsonSubTypes

Annotation used with JsonTypeInfo to indicate sub types of
serializable polymorphic types, and to associate logical names used
within JSON content (which is more portable than using physical Java
class names).

This is just another way to achieve the same result. The documentation you’re asking about states

Type ids that are based on Java class name are fairly
straight-forward: it’s just class name, possibly some simple prefix
removal (for “minimal” variant). But type name is different: one has
to have mapping between logical name and actual class.

So the various JsonTypeInfo.Id values that deal with class names are straight-forward because they can be auto-generated. For type names, however, you need to give the mapping value explicitly.

More Related Contents:

  1. Can not deserialize instance of java.util.ArrayList out of VALUE_STRING
  2. Jackson ObjectMapper DeserializationConfig.Feature.ACCEPT_EMPTY_STRING_AS_NULL_OBJECT
  3. How to use Jackson to deserialise an array of objects
  4. Java 8 LocalDate Jackson format
  5. Jackson – Deserialize using generic class
  6. Different names of JSON property during serialization and deserialization
  7. Date format Mapping to JSON Jackson
  8. Deserialize JSON with Jackson into Polymorphic Types – A Complete Example is giving me a compile error
  9. JsonMappingException: No suitable constructor found for type [simple type, class ]: can not instantiate from JSON object
  10. Parsing JSON in Java without knowing JSON format
  11. Jackson JSON Deserialization with Root Element
  12. Deserialize Java 8 LocalDateTime with JacksonMapper
  13. Jackson Change JsonIgnore Dynamically
  14. Query a JSONObject in java
  15. How to modify JsonNode in Java?
  16. Jackson + Builder Pattern?
  17. JPA Transient Annotation and JSON
  18. Can we make object as key in map when using JSON?
  19. Can Jackson be configured to trim leading/trailing whitespace from all string properties?
  20. Removing JSON elements with jackson
  21. Jackson is not deserialising a generic list that it has serialised
  22. Jackson conditional @JsonUnwrapped
  23. Jackson @JsonProperty(required=true) doesn’t throw an exception
  24. JSON to JSON transformer
  25. Jsonpath with Jackson or Gson
  26. Jackson JSON serialization, recursion avoidance by level defining
  27. Json deserialization into other class hierarchy using Jackson
  28. JSON Jackson parse different keys into same field
  29. Jackson JSON Deserialization: array elements in each line
  30. How to prevent null values inside a Map and null fields inside a bean from getting serialized through Jackson

Leave a Comment