anchor.diff:  
   Some JMS providers, like IBM's WebSphere MQ need options to be set on
   the JMS destination. For example, you may need to specify the
  -targetClient option. Since targetClient is a WebSphere MQ option and not
  +`targetClient` option. Since `targetClient` is a WebSphere MQ option and not
   a Camel URI option, you need to set that on the JMS destination name
   like so:
   
   [source,java]
   -----------------------------------------------------------------------------------
  -...
  +// ...
   .setHeader("CamelJmsDestinationName", constant("queue:///MY_QUEUE?targetClient=1"))
   .to("wmq:queue:MY_QUEUE?useMessageIDAsCorrelationID=true");
   -----------------------------------------------------------------------------------
  
positive.code: 
  Through Camel 2.7.x, the default setting for `cacheLevelName` is
  `CACHE_CONSUMER`. You will need to explicitly set
  `cacheLevelName=CACHE_NONE`. +
   In Camel 2.8 onwards, the default setting for `cacheLevelName` is
  `CACHE_AUTO`. This default auto detects the mode and sets the cache
  level accordingly to:
  
  * CACHE_CONSUMER = if transacted=false
  * CACHE_NONE = if transacted=true
  
  So you can say the default setting is conservative. Consider using
  `cacheLevelName=CACHE_CONSUMER` if you are using non-XA transactions.
  
negative.code: 
  [source,java]
  ----------------------------------------------------------------------------------------
  from("file://inbox/order").to("jms:queue:order?messageConverter=#myMessageConverter");
  ----------------------------------------------------------------------------------------
  
  You can also use a custom message converter when consuming from a JMS
  