anchor.diff:  Consumers Configuration Options
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   
  -The SjmsConsumer Endpoint supports the following properties:
  +The SJMS consumer endpoint supports the following properties:
   
   [width="100%",cols="10%,10%,80%",options="header",]
   |=======================================================================
  
positive.code: ----
  
  To see the full example of its usage please refer to the
  https://svn.apache.org/repos/asf/camel/trunk/components/camel-sjms/src/test/java/org/apache/camel/component/sjms/it/ConnectionResourceIT.java[ConnectionResourceIT].
  
  [[SJMS-Session,Consumer,&ProducerPooling&CachingManagement]]
  Session, Consumer, & Producer Pooling & Caching Management
  
negative.code: the Camel JMS Component. This plugable strategy ensures that messages
  sent over the wire conform to the JMS Message spec.
  
  For the `exchange.in.header` the following rules apply for the header
  keys:
  
  * Keys starting with `JMS` or `JMSX` are reserved.
  * `exchange.in.headers` keys must be literals and all be valid Java
  identifiers (do not use dots in the key name).
  * Camel replaces dots & hyphens and the reverse when when consuming JMS
  messages:
  
  ** is replaced by _DOT_ and the reverse replacement when Camel consumes
  the message.
  ** is replaced by _HYPHEN_ and the reverse replacement when Camel
  consumes the message. +
  See also the option `jmsKeyFormatStrategy`, which allows use of your own
  custom strategy for formatting keys.
  
  For the `exchange.in.header`, the following rules apply for the header
  values:
  
  [[SJMS-MessageContent]]
  