camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From zregvart <...@git.apache.org>
Subject [GitHub] camel pull request #1504: CAMEL-10932 REST Swagger component
Date Fri, 03 Mar 2017 12:45:42 GMT
GitHub user zregvart opened a pull request:

    https://github.com/apache/camel/pull/1504

    CAMEL-10932 REST Swagger component

    Submitted for review, thanks in advance for your feedback :+1: 
    
    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:
    
        to("rest-swagger:getPetById?endpoint=https://api.petstore.com")
    
    Which would pick up the Swagger specification from `swagger.json` and
    try to find a single component that implements the `RestProducerFactory`
    SPI.
    
    Typical use case would be specifying the component to delegate to and
    the path to the specification file, assuming that client configured and
    added `petstore` component to the Camel context:
    
        to("rest-swagger:getPetById:apis/petstore.json?"
           + "endpoint=https://api.petstore.com"
           + "&componentName=petstore"
          )

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/zregvart/camel CAMEL-10932

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1504.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1504
    
----
commit d3daf72ecaacb2e9bd992037dfb169635b8d8e84
Author: Zoran Regvart <zregvart@apache.org>
Date:   2017-03-03T11:40:54Z

    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:
    
        to("rest-swagger:getPetById?endpoint=https://api.petstore.com")
    
    Which would pick up the Swagger specification from `swagger.json` and
    try to find a single component that implements the `RestProducerFactory`
    SPI.
    
    Typical use case would be specifying the component to delegate to and
    the path to the specification file, assuming that client configured and
    added `petstore` component to the Camel context:
    
        to("rest-swagger:getPetById:apis/petstore.json?"
           + "endpoint=https://api.petstore.com"
           + "&componentName=petstore"
          )

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message