anchor.diff:  ### Message Headers
   
   Any URI option can be provided in a message header for producer
  -endpoints with a *`CamelOlingo2.`* prefix.
  +endpoints with a *`CamelOlingo4.`* prefix.
   
   ### Message Body
   
   All result message bodies utilize objects provided by the underlying
  -http://olingo.apache.org/javadoc/odata2/index.html[Apache Olingo 2.0
  -API] used by the Olingo2Component. Producer endpoints can specify the
  +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
  
positive.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/OData/OData.svc
  | 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.
  
negative.code: |=======================================================================
  |Endpoint |Options |HTTP Method |Result Body Type
  
  |batch |data |POST with multipart/mixed batch request |java.util.List<org.apache.camel.component.olingo4.api.batch.Olingo4BatchResponse>
  
  |create |data, resourcePath |POST |org.apache.olingo.client.api.domain.ClientEntity for new entries
  org.apache.olingo.commons.api.http.HttpStatusCode for other OData resources
  
  |delete |resourcePath |DELETE |org.apache.olingo.commons.api.http.HttpStatusCode
  
  |merge |data, resourcePath |MERGE |org.apache.olingo.commons.api.http.HttpStatusCode
  
  |patch |data, resourcePath |PATCH |org.apache.olingo.commons.api.http.HttpStatusCode
  
  |read |queryParams, resourcePath |GET |Depends on OData resource being queried as described next
  
  |update |data, resourcePath |PUT |org.apache.olingo.commons.api.http.HttpStatusCode
  |=======================================================================
  
  ### OData Resource Type Mapping
  