From d459ebdf4a81e1b779db1c620051a7ab9fcba79d Mon Sep 17 00:00:00 2001 From: Artem Bilan Date: Thu, 12 Apr 2018 14:30:56 -0400 Subject: [PATCH] Fix NOTE typo in the Core Doc **Cherry-pick to 2.0.x** --- .../src/main/asciidoc/spring-cloud-stream-overview.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-cloud-stream-core-docs/src/main/asciidoc/spring-cloud-stream-overview.adoc b/spring-cloud-stream-core-docs/src/main/asciidoc/spring-cloud-stream-overview.adoc index 900e3e3e5..6c1418840 100644 --- a/spring-cloud-stream-core-docs/src/main/asciidoc/spring-cloud-stream-overview.adoc +++ b/spring-cloud-stream-core-docs/src/main/asciidoc/spring-cloud-stream-overview.adoc @@ -1665,7 +1665,7 @@ But what if the payload type matches the target type declared by the handler met payload is passed unmodified. While this sounds pretty straightforward and logical, keep in mind handler methods that take a `Message` or `Object` as an argument. By declaring the target type to be `Object` (which is an `instanceof` everything in Java), you essentially forfeit the conversion process. -NOTEDo not expect `Message` to be converted into some other type based only on the `contentType`. +NOTE: Do not expect `Message` to be converted into some other type based only on the `contentType`. Remember that the `contentType` is complementary to the target type. If you wish, you can provide a hint, which `MessageConverter` may or may not take into consideration.