Implement binary support in JacksonConverterFactory
#3411
Merged
+109
−11
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.
Closes #3403
What?
The
JacksonConverterFactory
now includes binary support.Why?
Previously, the
JacksonResponseBodyConverter
relied on acharStream
to convert the response body content, limiting its capability to handle binary data. This constraint necessitated text-formatted content for serialization, making it challenging to send binary data. Although workarounds existed, it is now possible to easily address this limitation by introducing support for binary data through the use of a customObjectMapper
.How?
charStream
tobyteStream
in theJacksonResponseBodyConverter
.mediaType
through a constructor parameter inJacksonRequestBodyConverter
.JacksonConverterFactory
, allowing the setting ofmediaType
through a nullable second parameter. This new function is called by other overloads to maintain backward compatibility.