Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-7722

Swagger v2 issue using http gateway

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • fuse-6.x-GA
    • jboss-fuse-6.3
    • Gateway
    • % %
    • Hide

      In a fresh Fuse installation:

      1. ${fuse_home}/bin/fuse
      2. Install the following features:
        features:install camel-swagger
        features:install swagger
        features:install camel-cxf
        features:install cxf-http
        features:install cxf-http-jetty
      3. Deploy "myService" artifact
      4. Deploy "secondService" artifact
      5. Check http://localhost:8181/cxf/myService/swagger.yaml url
      6. Check http://localhost:8181/cxf/secondService/swagger.yaml url

      Notes:

      • If you stop the first artifact deployed (myService in this case), you still will be watching his information in the secondService.
      • Service functionality works as expected, but customer requires the correct information displayed in each url.

      Refer to the case to reach the artifacts.

      Show
      In a fresh Fuse installation: ${fuse_home}/bin/fuse Install the following features: features:install camel-swagger features:install swagger features:install camel-cxf features:install cxf-http features:install cxf-http-jetty Deploy "myService" artifact Deploy "secondService" artifact Check http://localhost:8181/cxf/myService/swagger.yaml url Check http://localhost:8181/cxf/secondService/swagger.yaml url Notes: If you stop the first artifact deployed (myService in this case), you still will be watching his information in the secondService. Service functionality works as expected, but customer requires the correct information displayed in each url. Refer to the case to reach the artifacts.

    Description

      If there is two or mode swagger v2 rest services in the container (standalone or fabric ) and you are using HTTP Gateway to access them, you will only able to see the swagger file of the first one deployed.

      Example:

      1st deployed: http://localhost:8181/cxf/myService/swagger.yaml, shows:

      swagger: "2.0"
      info:
        description: "Camel CXFRS Demo :: A Red Hat JBoss Fuse 6.3.0 RESTful service that\
          \ handles operations on an IP address or a hostname"
        version: "1.0.0-SNAPSHOT"
        title: "RESTful IP/Hostname Service DEMO"
        contact:
          name: "example@redhat.com"
        license:
          name: "Apache 2.0 License"
          url: "http://www.apache.org/licenses/LICENSE-2.0.html"
      host: "example"
      basePath: "/cxf/myService"
      schemes:
      - "http"
      - "https"
      paths:
        /ipservice/example:
          get:
            operationId: "getExample"
            produces:
            - "application/json"
            - "application/xml"
            parameters:
            - name: "type"
              in: "query"
              required: false
              type: "string"
              default: "json"
            - name: "ip"
              in: "query"
              required: false
              type: "string"
            responses:
              default:
                description: "successful operation"
      

      2nd deployed: http://localhost:8181/cxf/secondService/swagger.yaml, shows the same info as the first one deployed:

      swagger: "2.0"
      info:
        description: "Camel CXFRS Demo :: A Red Hat JBoss Fuse 6.3.0 RESTful service that\
          \ handles operations on an IP address or a hostname"
        version: "1.0.0-SNAPSHOT"
        title: "RESTful IP/Hostname Service DEMO"
        contact:
          name: "example@redhat.com"
        license:
          name: "Apache 2.0 License"
          url: "http://www.apache.org/licenses/LICENSE-2.0.html"
      host: "example"
      basePath: "/cxf/myService"
      schemes:
      - "http"
      - "https"
      paths:
        /ipservice/example:
          get:
            operationId: "getExample"
            produces:
            - "application/json"
            - "application/xml"
            parameters:
            - name: "type"
              in: "query"
              required: false
              type: "string"
              default: "json"
            - name: "ip"
              in: "query"
              required: false
              type: "string"
            responses:
              default:
                description: "successful operation"
      

      Attachments

        Activity

          People

            johnpoth John Poth
            emunoz@redhat.com Elkin Dario Munoz Duarte
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: