anchor.diff:  context switching may cause unnecessary performance impacts without
   gaining benefit.
   
  -The producer endpoint is handled much differently though. With the
  -producer after each message is delivered to its destination the Exchange
  -is closed and there is no longer a reference to that message. To make a
  -available all the messages available for redelivery you simply enable
  -transactions on a Producer Endpoint that is publishing BatchMessages.
  -The transaction will commit at the conclusion of the exchange which
  -includes all messages in the batch list. Nothing additional need be
  -configured. For example:
  -
  -[source,java]
  -----
  -List<BatchMessage<String>> messages = new ArrayList<BatchMessage<String>>();
  -for (int i = 1; i <= messageCount; i++) {
  -    String body = "Hello World " + i;
  -    BatchMessage<String> message = new BatchMessage<String>(body, null);
  -    messages.add(message);
  -}
  -----
  -
  -Now publish the List with transactions enabled:
  -
  -[source,java]
  -----
  -template.sendBody("sjms:queue:batch.queue?transacted=true", messages);
  -----
   
   == Additional Notes
   
  
positive.code: 0. For example the following configuration will commit the Session every
  10 messages:
  
  [source]
  ----
  sjms:queue:transacted.batch.consumer?transacted=true&transactionBatchCount=10
  ----
  
negative.code: | *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean
  |===
  // component options: END
  
  
  // endpoint options: START
  