anchor.diff:  +++++++++++++++++++++
   
   If you wish to use durable topic subscriptions, you need to specify both
  -*clientId* and **durableSubscriptionName**. The value of the `clientId`
  +`clientId` and `durableSubscriptionName`. The value of the `clientId`
   must be unique and can only be used by a single JMS connection instance
   in your entire network. You may prefer to use
   http://activemq.apache.org/virtual-destinations.html[Virtual Topics]
  
positive.code: link:jms.html[JMS] with a link:dead-letter-channel.html[Dead Letter
  Channel], using a JMS queue as the Dead Letter Queue, then normally the
  caused Exception is not stored in the JMS message. You can, however, use
  the *transferExchange* option on the JMS dead letter queue to instruct
  Camel to store the entire link:exchange.html[Exchange] in the queue as a
  `javax.jms.ObjectMessage` that holds a
  `org.apache.camel.impl.DefaultExchangeHolder`. This allows you to
  
negative.code: 
  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
  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");
  -----------------------------------------------------------------------------------
  