anchor.diff:  
   Starting with _version 1.3_, some `MessageChannel` - based binders publish errors to a discrete error channel for each destination.
   In addition, these error channels are bridged to the global Spring Integration `errorChannel` mentioned above.
  -You can therefore consume errors for specific destinations and/or for all destinations, using a standard Spring Integration flow (`IntegrationFlow`, `@ServiceActivator`, etc).
  +You can therefore consume errors for specific destinations and/or for all destinations, using a standard Spring Integration flow (`IntegrationFlow`, `@ServiceActivator`, etc.).
   
   On the consumer side, the listener thread catches any exceptions and forwards an `ErrorMessage` to the destination's error channel.
   The payload of the message is a `MessagingException` with the normal `failedMessage` and `cause` properties.
  
positive.code: }
  ----
  
  Once the 'namespace' is set for the individual applications, the application properties with the `namespace` as prefix can be passed to the aggregate application using any supported property source (commandline, environment properties etc.,)
  
  For instance, to override the default `fixedDelay` and `debug` properties of 'source' and 'sink' applications:
  
  
negative.code: |===
  |`content-type` header | MessageConverter | Supported target type | Comments
  
  |application/json
  |CustomMappingJackson2MessageConverter
  | POJO or String
  |
  