anchor.diff:  
   Any of the endpoint options can be provided in either the endpoint URI,
   or dynamically in a message header. The message header name must be of
  -the format *`CamelOlingo2.<option>`*. Note that the *`inBody`* option
  +the format *`CamelOlingo4.<option>`*. Note that the *`inBody`* option
   overrides message header, i.e. the endpoint
   option *`inBody=option`* would override
  -a *`CamelOlingo2.option`* header. In addition, query parameters can be
  +a *`CamelOlingo4.option`* header. In addition, query parameters can be
   specified 
   
   Note that the resourcePath option can either in specified in the URI as
   a part of the URI path, as an endpoint option
   ?resourcePath=<resource-path> or as a header value
  -CamelOlingo2.resourcePath. The OData entity key predicate can either be
  +CamelOlingo4.resourcePath. The OData entity key predicate can either be
   a part of the resource path, e.g. _Manufacturers('1')_, where _'__1'_ is
   the key predicate, or be specified separately with resource path
   _Manufacturers_ and keyPredicate option _'1'_. 
  
positive.code: |=======================================================================
  |OData Resource Type |Resource URI from resourcePath and keyPredicate |In or Out Body Type
  
  |Entity data model |$metadata |org.apache.olingo.odata2.api.edm.Edm
  
  |Service document |/ |org.apache.olingo.odata2.api.servicedocument.ServiceDocument
  
  |OData feed |<entity-set> |org.apache.olingo.odata2.api.ep.feed.ODataFeed
  
  |OData entry |<entity-set>(<key-predicate>) |org.apache.olingo.odata2.api.ep.entry.ODataEntry for Out body (response)
  java.util.Map<String, Object> for In body (request)
  
  |Simple property |<entity-set>(<key-predicate>)/<simple-property> |Appropriate Java data type as described by Olingo EdmProperty
  
  |Simple property value |<entity-set>(<key-predicate>)/<simple-property>/$value |Appropriate Java data type as described by Olingo EdmProperty
  
  |Complex property |<entity-set>(<key-predicate>)/<complex-property> |java.util.Map<String, Object>
  
  |Zero or one association link |<entity-set>(<key-predicate>/$link/<one-to-one-entity-set-property> |String for response
  java.util.Map<String, Object> with key property names and values for request
  
  |Zero or many association links |<entity-set>(<key-predicate>/$link/<one-to-many-entity-set-property> |java.util.List<String> for response
  java.util.List<java.util.Map<String, Object>> containing list of key property names and values for request
  
  |Count |<resource-uri>/$count |java.lang.Long
  |=======================================================================
  
negative.code: | httpHeaders | common |  | Map | Custom HTTP headers to inject into every request this could include OAuth tokens etc.
  | inBody | common |  | String | Sets the name of a parameter to be passed in the exchange In Body
  | proxy | common |  | HttpHost | HTTP proxy server configuration
  | serviceUri | common |  | String | Target OData service base URI e.g. http://services.odata.org/TripPinRESTierService/
  | socketTimeout | common | 30000 | int | HTTP request timeout in milliseconds defaults to 30000 (30 seconds)
  | sslContextParameters | common |  | SSLContextParameters | To configure security using SSLContextParameters
  | bridgeErrorHandler | consumer | false | boolean | Allows for bridging the consumer to the Camel routing Error Handler which mean any exceptions occurred while the consumer is trying to pickup incoming messages or the likes will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions that will be logged at WARN or ERROR level and ignored.
  