Consider Kotlinx Serialization for JSON as a Jackson/Gson/Jsonb equivalent #34410
Assignees
Labels
in: web
Issues in web modules (web, webmvc, webflux, websocket)
type: enhancement
A general enhancement
Milestone
Comments
bclozel
added
in: web
This was referenced Feb 17, 2025
sdeleuze
added a commit
to sdeleuze/spring-framework
that referenced
this issue
Feb 17, 2025
This commit introduces open polymorphism support with Kotlin Serialization in HTTP converters and codecs as a follow-up of spring-projectsgh-34410 which considers Kotlin Serialization as a Jackson/Gson/Jsonb equivalent (it is not anymore configured before Jackson). Closes spring-projectsgh-34433
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#21188 added support and auto-detection for Kotlinx Serialization.
As seen in spring-projects/spring-boot#24238, this is causing too much issues when Spring applications are consuming kotlin libraries bringing this dependency transitively. This converter shadows Jackson for Java enums, even after changes made in #26147.
This means we should consider this converter like Gson and Jsonb: a fallback replacement if Jackson is not present. Spring users can still add this converter to the list; we just won't make the mere presence of this library on the classpath as a strong enough signal. Spring Boot users can use
HttpMessageConvertersto add/alter the list of converters.Because this is a breaking change, I'm scheduling this for 7.0.
The text was updated successfully, but these errors were encountered: