Clone Tools
  • last updated 28 mins ago
Constraints: committers
Constraints: files
Constraints: dates
CAMEL-11091 REST Swagger handling of empty spec...


The specificatonUri for endpoint URIs starting with `#` in the remaining

part of the URI (i.e. `rest-swagger:#getPetById`) now default to


  1. … 1 more file in changeset.
CAMEL-11051 Support query parameters in rest-sw...


Adds REST endpoint `queryParameters` property based on the Swagger

specification. It is expected that the same-named parameters are present

in the headers of the incoming message.

  1. … 1 more file in changeset.
CAMEL-10932 REST Swagger component

This includes the initial implementation of the `rest-swagger` component

that allows for a higher level abstraction over the REST API usage from

other Camel components that implement the `RestProducerFactory` SPI

combined with Swagger (Open API) specifications.

The most simple usage would be:


Which would pick up the Swagger specification from `swagger.json` and

try to find a single component that implements the `RestProducerFactory`

SPI and invoke the `getPetById` operation.

Other way of using this component could be:


That loads the Swagger specification from the

`` URL and invokes the

`getPetById` operation.

More concise way of configuring would be to configure most properties

on the component add it to CamelContext, and use only `operationId` path

parameter when triggering the exchange:

// add `petstore` component to the CamelContext

RestSwaggerComponent petstore =

new RestSwaggerComponent(camelContext);



camelContext.addComponent("petstore", petstore);

And then use `operationId` in endpoint definition:

ProducerTemplate template = camelContext.getProducerTemplate();

template.requestBodyAndHeaders("petstore:getPetById", null, "petId",


    • -0
    • +152
    • -0
    • +336
    • -0
    • +66
    • -0
    • +50
  1. … 25 more files in changeset.