anchor.diff:  ProducerTemplate template;
   
   String getPetJsonById(int petId) {
  -    return template.requestBodyAndHeaders("petstore:getPetById", null, "petId", petId);
  +    return template.requestBodyAndHeader("petstore:getPetById", null, "petId", petId);
   }
   ----
   
  
positive.code: 
  == Example: PetStore
  
  Checkout the example in the `camel-example-rest-openapi` project in
  the `examples` directory.
  
  For example if you wanted to use the 
  https://petstore3.swagger.io/api/v3/[_PetStore_] provided REST API simply
  reference the specification URI and desired operation id from the
  OpenApi specification or download the specification and store it as
  `openapi.json` (in the root) of CLASSPATH that way it will be 
  automaticaly used. Let's use the xref:undertow-component.adoc[Undertow]
  component to perform all the requests and Camels excelent support for 
  Spring Boot.
  
  Here are our dependencies defined in Maven POM file:
  
negative.code: [NOTE]
  ====
  Support in Camel for Spring Boot will auto create the 
  `HttpComponent` Spring bean, and you can configure it using
  `application.properties` (or `application.yml`) using prefix
  `camel.component.http.`. We are defining the `petstore`
  component here in order to have a named component in the Camel context
  that we can use to interact with the PetStore REST API, if this is the
  only `rest-openapi` component used we might configure it in the same
  manner (using `application.properties`).
  
  In this example, there is no need to explicitly associate the `petstore`
  component with the `HttpComponent` as Camel will use the first class on 
  the CLASSPATH that implements `RestProducerFactory`. However, if a different
  component is required, then calling `petstore.setComponentName("http")` 
  would use the named component from the Camel registry.
  
  ====
  
  Now in our application we can simply use the `ProducerTemplate` to
  