anchor.diff:  http://www.mongodb.org/display/DOCS/Updating#Updating-ModifierOperations[modifier
   operations] from MongoDB are supported.
   
  -NOTE: *Multiupdates* . By default, MongoDB will only update 1 object even if multiple objects
  +[NOTE]
  +====
  +*Multiupdates* 
  +
  +By default, MongoDB will only update 1 object even if multiple objects
   match the filter query. To instruct MongoDB to update *all* matching
   records, set the `CamelMongoDbMultiUpdate` IN message header to `true`.
  +====
  +
   
   A header with key `CamelMongoDbRecordsAffected` will be returned
   (`MongoDbConstants.RECORDS_AFFECTED` constant) with the number of
  
positive.code: *Both producer and consumer is supported*
  // HEADER END
  
  Note: MongoDB Camel component Use the Mongo Driver for Java 3.x.
  
  According to Wikipedia: "NoSQL is a movement promoting a loosely defined
  class of non-relational data stores that break with a long history of
  
negative.code: You can define the filter using MongoDBConstants.CRITERIA header as `Bson`
  and define the update rules as `Bson` in Body.
  
  [NOTE]
  ====
  *Update after enrich*
  
  While defining the filter by using MongoDBConstants.CRITERIA header as `Bson`
  to query mongodb before you do update, you should notice you need to remove it from the resulting camel exchange 
  during aggregation if you use enrich pattern with a aggregation strategy and then apply mongodb update. 
  If you don't remove this header during aggregation and/or redefine MongoDBConstants.CRITERIA header before sending
  camel exchange to mongodb producer endpoint, you may end up with invalid camel exchange payload while updating mongodb. 
  ====
  
  
  The second way Require a
  List<Bson> as the IN message body containing exactly 2 elements:
  