Refine naming consistency for HttpRequestFactories and update RestOperations interface #33411
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses issue #33382 by refining the naming consistency within the Spring Framework.
Class Renaming
ReactorNettyClientRequestFactory
->ReactorClientHttpRequestFactory
ReactorClientHttpConnector
->ReactorNettyClientHttpConnector
HttpComponentsClientHttpRequestFactory
->HttpComponentsClientRequestFactory
RestOperations
Interface UpdateUpdated the
RestOperations
interface to reflect the new class names, specifically changing references fromHttpComponentsClientHttpRequestFactory
toHttpComponentsClientRequestFactory
.This update affects 32 files.
Testing
All relevant tests were executed locally using
./gradlew test
, and all tests passed successfully. No regressions were introduced by the changes in this PR.Issue: #33382