anchor.diff:  ----------------------------------------------
       <dependency>
           <groupId>org.apache.camel</groupId>
  -        <artifactId>camel-olingo2</artifactId>
  +        <artifactId>camel-olingo4</artifactId>
           <version>${camel-version}</version>
       </dependency>
   ----------------------------------------------
  
positive.code: 
  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
  overrides message header, i.e. the endpoint
  option *`inBody=option`* would override
  a *`CamelOlingo2.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
  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'_. 
  
negative.code: ### Message Headers
  
  Any URI option can be provided in a message header for producer
  endpoints with a *`CamelOlingo4.`* prefix.
  
  ### Message Body
  
  All result message bodies utilize objects provided by the underlying
  http://olingo.apache.org/javadoc/odata4/index.html[Apache Olingo 4.0
  API] used by the Olingo4Component. Producer endpoints can specify the
  option name for incoming message body in the *`inBody`* endpoint URI
  parameter. For endpoints that return an array or collection, a consumer
  endpoint will map every element to distinct messages, unless
  