Master JSON Field Adaptation in Spring Boot: 3 Powerful Techniques

Introduction : In microservice and front‑back separation era, JSON is the common language, but mismatched field names cause backend parsing failures.

Three solutions are presented for flexible JSON field adaptation in Spring Boot:

Solution 1: Map reception

Use Map<String, Object> to store extra fields.

{</code><code>  "name": "icoderoad",</code><code>  "mobile": "13900000000",</code><code>  "extFields": {</code><code>    "email": "[email protected]",</code><code>    "age": 22</code><code>  }</code><code>}

Entity class adds a protected Map<String, Object> extFields; field and controller returns the object.

Advantages: simple, lightweight. Disadvantages: readability suffers, code can become bulky.

Solution 2: JsonNode reception

When JSON structure is deep or variable, use Jackson's JsonNode.

Add Maven dependency com.fasterxml.jackson.core:jackson-databind:2.13.0 and change the entity field to private JsonNode extFields;. Controller remains similar.

Advantages: can parse any depth, dynamic node access, tight Jackson integration. Disadvantages: more complex, steeper learning curve.

Solution 3: @JsonAnySetter / @JsonAnyGetter

These annotations let the object dynamically receive and output unknown fields.

@JsonAnySetter
public void setUnknownField(String key, Object value) {
    extFields.put(key, value);
}
@JsonAnyGetter
public Map<String, Object> getUnknownFields() {
    return extFields;
}

Provides flexible, maintainable handling for frequently changing fields.

Example: an online shop product JSON with nested promotionInfo can be mapped either with a Map or a JsonNode for deeper access.

Conclusion : By choosing the appropriate technique—Map for lightweight cases, JsonNode for complex structures, or @JsonAnySetter/@JsonAnyGetter for dynamic extensions—developers can adapt JSON fields in Spring Boot without nightmares.