From 35dff8762a643efc0c1f3d6f1724630f0141e7db Mon Sep 17 00:00:00 2001 From: Clemens Diebold <46743155+clemensdiebold@users.noreply.github.com> Date: Fri, 5 Jul 2019 12:06:03 +0200 Subject: [PATCH] Fixes some small typos --- docs/src/main/asciidoc/spring-cloud-stream.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/main/asciidoc/spring-cloud-stream.adoc b/docs/src/main/asciidoc/spring-cloud-stream.adoc index 7ee856731..b0ac8c12a 100644 --- a/docs/src/main/asciidoc/spring-cloud-stream.adoc +++ b/docs/src/main/asciidoc/spring-cloud-stream.adoc @@ -1392,7 +1392,7 @@ To avoid repetition, Spring Cloud Stream supports setting values for all channel When it comes to avoiding repetitions for extended binding properties, this format should be used - `spring.cloud.stream..default..=`. -In what follows, we indicate where we have omitted the `spring.cloud.stream.bindings..` prefix and focus just on the property name, with the understanding that the prefix ise included at runtime. +In what follows, we indicate where we have omitted the `spring.cloud.stream.bindings..` prefix and focus just on the property name, with the understanding that the prefix is included at runtime. ==== Common Binding Properties @@ -1762,7 +1762,7 @@ However, it also provides a sensible default (which was determined from communit Another reason for making `application/json` the default stems from the interoperability requirements driven by distributed microservices architectures, where producer and consumer not only run in different JVMs but can also run on different non-JVM platforms. -When the non-void handler method returns, if the the return value is already a `Message`, that `Message` becomes the payload. However, when the return value is not a `Message`, the new `Message` is constructed with the return value as the payload while inheriting +When the non-void handler method returns, if the return value is already a `Message`, that `Message` becomes the payload. However, when the return value is not a `Message`, the new `Message` is constructed with the return value as the payload while inheriting headers from the input `Message` minus the headers defined or filtered by `SpringIntegrationProperties.messageHandlerNotPropagatedHeaders`. By default, there is only one header set there: `contentType`. This means that the new `Message` does not have `contentType` header set, thus ensuring that the `contentType` can evolve. You can always opt out of returning a `Message` from the handler method where you can inject any header you wish.