spring-http-interface: introduce springHttpClientAdapter, fix paramDoc.mustache

[ibaranga]

Addressing issue #19712

What

• Introduce springHttpClientAdapter useHttpServiceProxyFactoryInterfacesConfigurator for spring-http-interface
• Added an spring-http-interface-specific empty paramDoc.mustache

Why

• Enable selecting different HTTP client implementations when generating Spring HTTP client interfaces
• Provides additional flexibility for users who want to generate non-reactive Spring Boot applications

How

- springHttpClientAdapter: Allows users to choose between different HTTP client implementations used in HttpInterfacesAbstractConfigurator:
- web-client (set by default, to ensure backward compatibility)
- rest-client
- rest-template
- Separate templates for each HttpInterfacesAbstractConfigurator implementation:
- httpInterfacesRestClientConfiguration.mustache
- httpInterfacesRestTemplateConfiguration.mustache
- httpInterfacesWebClientConfiguration.mustache
- Log warning for configuration mismatch
- When reactive: false is used in combination with the reactive web-client, it warns users of potential configuration
mismatches, and suggests switching to rest-template or rest-client for non-reactive configurations.

• spring-http-interface: introduce springHttpClientAdapter, fix paramDoc.mustache #19710 (comment)

• Remove unnecessary paramDoc

  • Added an spring-http-interface-specific empty paramDoc.mustache in JavaSpring/libraries/spring-http-interface/paramDoc.mustache
  • This prevents inheriting the @Parameter annotations from the default Spring template located at JavaSpring/paramDoc.mustache.
  • Otherwise, the generated code includes @Parameter annotations on request body parameters, which were causing compile errors due to missing imports

---

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package 
  ./bin/generate-samples.sh ./bin/configs/*.yaml
  ./bin/utils/export_docs_generators.sh
  

  (For Windows users, please run the script in Git BASH)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

@cachescrubber @welshm @MelleD @atextor @manedev79 @javisst @borsch @banlevente @Zomzog @martin-mfg

[ibaranga]

This is marked as deprecated, replacing it with builderFor, which is also in line with the rest of the httpInterfaces*Configuration.mustache templates

[wing328]

please review the errors when you've time: https://github.com/OpenAPITools/openapi-generator/actions/runs/11094295717/job/30896757555?pr=19710

[ibaranga]

@wing328 thanks, fixed!

[wing328]

please review the errors reported by the CI when you've time.

[ibaranga]

please review the errors reported by the CI when you've time.

Thanks again, @wing328, I've just updated the PR!

[wing328]

filed #20129 to trigger all the tests

let's see how that goes

[wing328]

@ibaranga can you please add sample to test the new option similar to #20071 (comment) ?

[davidkarlsen]

It would be good to test this with latest GA version of spring, as #20174 is related

[wing328]

@davidkarlsen do you mind doing a test locally for that?

git checkout -b ibaranga-master master
git pull https://github.com/ibaranga/openapi-generator.git master

[dejavuhuh]

Do you have any plans to support Kotlin?🤔

[Picazsoo]

Do you have any plans to support Kotlin?🤔

I just opened an issue here and plan to contribute a PR with barebones implementation of kotlin-spring declarative http interface in coming days.

[Bragolgirith]

Hi, it seems this PR was close to being merged about a year ago, but hasn’t been updated since.
What is the current blocker? Is there anything I can do to help move it forward?

[wing328]

@Bragolgirith can you please file a new one based on this PR with resolved merged conflicts?

[Bragolgirith]

I wouldn't want to steal the attribution from the original PR author, so (for now) I've now created a PR to @ibaranga's fork with the following changes:

• Merged from master and resolved conflicts
• Added a check to fail early if a Spring Boot version other than 3 or 4 is used

@ibaranga Would you be willing to take a look and - if at all possible - merge it soon-ish? :)

[ibaranga]

Thanks @Bragolgirith - merged!

[wing328]

I wouldn't want to steal the attribution from the original PR author

@ibaranga will be listed as co-author in your (@Bragolgirith) PR. That's how git works.

Just triggered the workflow. Will merge if all tests pass.

[ibaranga]

I wouldn't want to steal the attribution from the original PR author

@ibaranga will be listed as co-author in your (@Bragolgirith) PR. That's how git works.

Just triggered the workflow. Will merge if all tests pass.

Thanks @wing328 !

Just pushed a few follow-up fixes to satisfy the spring-http-interface early-checks ("Requires Spring Boot 3 or 4."):

• Set useSpringBoot3: "true" for all relevant sample configs and regenerated the samples.

• Updated the docs in java-camel.md and spring.md to explicitly state the Spring Boot 3 or 4 requirement.

All checks (except docker/maven publish) are passing on my fork.