GH-3483: Fallback to RestTemplate.converters (#3485)
* GH-3483: Fallback to RestTemplate.converters Fixes https://github.com/spring-projects/spring-integration/issues/3483 When there is no reasonable way to determine a `Content-Type` from the request message, do not set an `application/x-java-serialized-object` as a fallback and let the `RestTemplate` to determine the target type and conversion through its `HttpMessageConverter` set * Remove `application/x-java-serialized-object` fallback from the `AbstractHttpRequestExecutingMessageHandler` * Adjust its log messages according `LogAccessor` * Un`@Disable` `WebFluxDslTests` since fix was done in Spring Security * Add `HttpRequestExecutingMessageHandlerTests.testNoContentTypeAndSmartConverter()` * Mention change in `What's New` * Fix language in whats-new.adoc Co-authored-by: Gary Russell <grussell@vmware.com> Co-authored-by: Gary Russell <grussell@vmware.com>
This commit is contained in:
@@ -36,3 +36,10 @@ See <<./amqp.adoc#amqp,AMQP Support>> for more information.
|
||||
|
||||
The `ReactiveRedisStreamMessageProducer` has now setters for all the `StreamReceiver.StreamReceiverOptionsBuilder` options, including an `onErrorResume` function.
|
||||
See <<./redis.adoc#redis,Redis Support>> for more information.
|
||||
|
||||
[[x5.5-http]]
|
||||
==== HTTP Changes
|
||||
|
||||
The `HttpRequestExecutingMessageHandler` doesn't fallback to the `application/x-java-serialized-object` content type any more and lets the `RestTemplate` make the final decision for the request body conversion based on the `HttpMessageConverter` provided.
|
||||
|
||||
See <<./http.adoc#http,HTTP Support>> for more information.
|
||||
|
||||
Reference in New Issue
Block a user