anchor.diff:  * Through its `contentType` settings on inbound and outbound channels
   * Through its argument mapping performed for methods annotated with `@StreamListener`
   
  -Spring Cloud Stream allows you to declaratively configure type conversion for inputs and outputs using the `content-type` property of a binding.
  +Spring Cloud Stream allows you to declaratively configure type conversion for inputs and outputs using the `spring.cloud.stream.bindngs.<channelName>.content-type` property of a binding.
   Note that general type conversion may also be accomplished easily by using a transformer inside your application.
   Currently, Spring Cloud Stream natively supports the following type conversions commonly used in streams:
   
  
positive.code: 
  Besides the conversions that it supports out of the box, Spring Cloud Stream also supports registering your own message conversion implementations.
  This allows you to send and receive data in a variety of custom formats, including binary, and associate them with specific `contentTypes`.
  In order to do so, you can create a class that extends `AbstractMessageConverter`
  
  === Schema-based message converters
  
  
negative.code: 
  For using it, you can simply add it to the application context, optionally specifying one ore more `MimeTypes` to associate it with.
  The default `MimeType` is `application/avro`.
  Here is an example of configuring it in a sink application registering the Apache Avro MessageConverter, without a predefined schema:
  
  [source,java]
  ----
  