anchor.diff:  </dependency>
   ----
   
  -Start by defining the _Undertow_ component and the
  -_RestOpenApiComponent_:
  +Start by defining a _RestOpenApiComponent_ bean:
   
   [source,java]
   ----
   @Bean
  -public Component petstore(CamelContext camelContext, UndertowComponent undertow) {
  +public Component petstore(CamelContext camelContext) {
       RestOpenApiComponent petstore = new RestOpenApiComponent(camelContext);
  -    petstore.setSpecificationUri("https://petstore3.swagger.io/api/v3/openapi.json");
  -    petstore.setDelegate(undertow);
  -
  +    petstore.setSpecificationUri(new URI("https://petstore3.swagger.io/api/v3/openapi.json"));
  +    petstore.setHost("https://petstore3.swagger.io");
       return petstore;
   }
   ----
  
positive.code: ProducerTemplate template;
  
  String getPetJsonById(int petId) {
      return template.requestBodyAndHeaders("petstore:getPetById", null, "petId", petId);
  }
  ----
  
  
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
  