anchor.diff:  The benefit of doing so is that the cacheLevel setting will be honored
   when using local transactions without a configured TransactionManager.
   When a TransactionManager is configured, no caching happens at DMLC
  -level and its necessary to rely on a pooled connection factory. For more
  -details about this kind of setup see
  +level and it is necessary to rely on a pooled connection factory. For more
  +details about this kind of setup, see
   http://tmielke.blogspot.com/2012/03/camel-jms-with-transactions-lessons.html[here]
   and
   http://forum.springsource.org/showthread.php?123631-JMS-DMLC-not-caching%20connection-when-using-TX-despite-cacheLevel-CACHE_CONSUMER&p=403530&posted=1#post403530[here].
  
positive.code: 
  
  // component options: START
  The JMS component supports 80 options which are listed below.
  
  
  
  
negative.code: 
  [source,java]
  ----------------------------------------------------------------------------------------
  // we need to pass in the JMS component, and in this sample we use ActiveMQ
  JmsEndpoint endpoint = JmsEndpoint.newInstance(replyDestination, activeMQComponent);
  // now we have the endpoint we can use regular Camel API to send a message to it
  template.sendBody(endpoint, "Here is the late reply.");
  ----------------------------------------------------------------------------------------
  
  A different solution to sending a reply is to provide the
  