From fcc1b6fe2bf67767c612230156ce169b6b81fb40 Mon Sep 17 00:00:00 2001 From: Guilherme Torres Castro Date: Sun, 10 May 2020 18:12:17 -0300 Subject: [PATCH] Remove duplicate property in documentation --- docs/src/main/asciidoc/spring-cloud-stream.adoc | 8 -------- 1 file changed, 8 deletions(-) diff --git a/docs/src/main/asciidoc/spring-cloud-stream.adoc b/docs/src/main/asciidoc/spring-cloud-stream.adoc index 1754b11d1..4f0259446 100644 --- a/docs/src/main/asciidoc/spring-cloud-stream.adoc +++ b/docs/src/main/asciidoc/spring-cloud-stream.adoc @@ -2463,14 +2463,6 @@ When set to `headers`, it uses the middleware's native header mechanism. When set to `embeddedHeaders`, it embeds headers into the message payload. + Default: Depends on the binder implementation. -useNativeEncoding:: -When set to `true`, the outbound message is serialized directly by the client library, which must be configured correspondingly (for example, setting an appropriate Kafka producer value serializer). -When this configuration is being used, the outbound message marshalling is not based on the `contentType` of the binding. -When native encoding is used, it is the responsibility of the consumer to use an appropriate decoder (for example, the Kafka consumer value de-serializer) to deserialize the inbound message. -Also, when native encoding and decoding is used, the `headerMode=embeddedHeaders` property is ignored and headers are not embedded in the message. -See the consumer property `useNativeDecoding`. -+ -Default: `false`. useNativeEncoding:: When set to `true`, the outbound message is serialized directly by the client library, which must be configured correspondingly (for example, setting an appropriate Kafka producer value serializer).