Use SmartHttpMessageConverter
over GenericHttpMessageConverter
where possible
#18075
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.
We want to use
SmartHttpMessageConverter
overGenericHttpMessageConverter
.To get there, we first need to see the classes where
GenericHttpMessageConverter
is still used. These areHttpConverters
with the methodsstatic GenericHttpMessageConverter<Object> getJsonMessageConverter()
. If we directly replace the return value withSmartHttpMessageConverter
, we will see that some classes directly useGenericHttpMessageConverter
and its methods.To do this, I decided to create a special adapter
SmartGenericHttpMessageConverterAdapter
into which we can passGenericHttpMessageConverter
and use it asSmartHttpMessageConverter
. We need this for classes that inherit fromGenericHttpMessageConverter
. However, for those who use jackson3, we can directly returnJacksonJsonHttpMessageConverter
, which in turn inherits fromSmartHttpMessageConverter
.Closes: gh-18073