The third lecture of the first session in Part 2 of the [Modern Backend] course, "Spring Boot 4.0 Overview (3)," covers runtime risks and standardization.
This lecture focuses on the changes to the Jackson 3 serialization/deserialization engine that backend developers need to pay the closest attention to during the transition to Spring Boot 4.0, as well as the newly introduced JSpecify-based null-safety standard.
📌 Key learning topics:
-
10.5 Jackson 3 Migration Strategy:
-
Package namespace
tools.jackson) and annotation package exceptions -
the benefits of code cleanup resulting from the transition from Checked Exception to Unchecked Exception (
JacksonException) -
Critical runtime defects that the compiler cannot detect (Type C): changes to the default date format (number → ISO 8601 string) and stricter trailing-token validation (strict parsing)
-
The framework-level roadmap for deferring Jackson 2 support and removing it completely (7.2)
-
10.6 Introducing JSpecify and Strengthening Null Safety:
-
The split-package issues of JSR 305 and the complete transition to the JSpecify standard
-
Differences in impact between the Java environment (which generates warnings) and the Kotlin environment (which generates compilation errors), along with a guide to gradual migration
Please take an in-depth look at how to prevent and respond to silent defects in which compilation succeeds but the API response specification breaks at runtime.