[REQ][Kotlin][jvm-spring-webclient] Support for useSpringBoot4 and useJackson3

Aperta
  • Qualcosa non va?
#25,078 0 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
45/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
kotlin, spring, spring-boot
Ambito
tooling

Direzione di ricerca

Start at the Kotlin generator path for library=jvm-spring-webclient and inspect how useSpringBoot3, Jackson types, WebClient codecs, and generated build dependencies are selected. Compare the existing Spring Boot 3 handling with the requested useSpringBoot4 and useJackson3 options, then verify generated code and dependencies for both flags and their defaults.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Enhancement: Feature
Is your feature request related to a problem? Please describe.

Spring Boot 4 (Spring Framework 7) is now GA and uses Jackson 3 (tools.jackson.*) as its default JSON library, while Jackson 2 support in Spring Framework 7 is deprecated.

The Kotlin client generator with library=jvm-spring-webclient currently offers only useSpringBoot3. The generated code is tied to Spring Boot 3 and Jackson 2, so it uses:

  • com.fasterxml.jackson.databind.ObjectMapper and related com.fasterxml.jackson.databind.* types
  • Jackson2JsonEncoder / Jackson2JsonDecoder for WebClient codecs
  • com.fasterxml.jackson.module:jackson-module-kotlin and jackson-datatype-jsr310 in the generated build files

This causes problems when the generated client is used in a Spring Boot 4 application:

  • Two Jackson major versions end up on the classpath (Jackson 2 for the generated client and Jackson 3 for the application).
  • The application's auto-configured JsonMapper and its customizations can't be reused by the generated client.
  • The generated code depends on deprecated Spring APIs (Jackson2JsonEncoder / Jackson2JsonDecoder), which will likely be removed in a future Spring release.

I'm always frustrated when I have to post-process generated sources or maintain custom templates just to make the client compile cleanly and work with Spring Boot 4.

Describe the solution you'd like

Add two new options for the Kotlin client generator with library=jvm-spring-webclient:

  1. useSpringBoot4 (default false): generates code and build files targeting Spring Boot 4 / Spring Framework 7.
  2. useJackson3 (default false, possibly implied by useSpringBoot4): generates code using Jackson 3, including:
    • tools.jackson.databind.json.JsonMapper (immutable, built via builder) instead of ObjectMapper
    • JacksonJsonEncoder / JacksonJsonDecoder instead of Jackson2JsonEncoder / Jackson2JsonDecoder
    • the tools.jackson.module:jackson-module-kotlin dependency
    • no separate jackson-datatype-jsr310, since Java time support is built into Jackson 3 core
    • annotations kept as com.fasterxml.jackson.annotation.*, which Jackson 3 still uses

The generated client would then be able to accept a JsonMapper from the application context, as it can with an ObjectMapper today.

Example configuration:

generatorName: kotlin
library: jvm-spring-webclient
additionalProperties:
  useSpringBoot4: true
  useJackson3: true
  serializationLibrary: jackson

Describe alternatives you've considered

  • Keeping Jackson 2 alongside Jackson 3: this works for now, but it duplicates dependencies, splits mapper configuration, and relies on deprecated Spring APIs.
  • Custom templates (templateDir): this is possible, but every user has to maintain a fork of the templates and keep it in sync with upstream changes.
  • Switching to kotlinx_serialization: this means a large change to the existing models and doesn't fit projects standardized on Jackson.
  • Using a different library (e.g. jvm-spring-restclient): this isn't an option for reactive code based on WebClient.

Additional context

Component Version
OpenAPI Generator 7.x.x
Spring Boot 4.0.x
Kotlin 2.x

Question: Is this on the roadmap, and roughly when could support for useSpringBoot4 / useJackson3 in jvm-spring-webclient be expected?

If it helps, I'm happy to contribute a PR given some guidance on the preferred approach:

  • Should useJackson3 be a separate flag, or implied by useSpringBoot4?
  • Should the implementation be aligned with how other Spring-based generators handle Spring Boot 4 / Jackson 3?
Lingua principale
Java
Stelle
26.9k
Fork
7.8k
Merge medio
2g 10h
PR unite (30g)
180

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenAPITools/openapi-generator

Tutte le issue di OpenAPITools/openapi-generator

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.