anchor.diff:  NOTE: If `group` is not specified anonymous group is used (something like `input.anonymous.2K37rb06Q6m2r51-SPIDDQ`), which is not suitable for error
   handling scenarious, since you don't know what it's going to be until the destination is created.
   
  -Also, in the event you are binidng to the existing destination such as:
  +Also, in the event you are binding to the existing destination such as:
   
   [source,text]
   ----
  
positive.code: 
  the full destination name is `myFooDestination.myGroup` and then the dedicated error channel name is `myFooDestination.myGroup.errors`.
  
  Back to the example. . .
  
  The `handle(..)` method, which subscribes to the channel named `input`, throws an exception.  Given there is also a subscriber to the error channel `input.myGroup.errors`
  all error messages are handled by this subscriber.
  
negative.code: +
  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`.
  errorChannelEnabled::
  