Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3B76D187A3 for ; Fri, 15 Jan 2016 13:22:40 +0000 (UTC) Received: (qmail 84393 invoked by uid 500); 15 Jan 2016 13:22:40 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 84360 invoked by uid 500); 15 Jan 2016 13:22:40 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 84086 invoked by uid 99); 15 Jan 2016 13:22:40 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jan 2016 13:22:40 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D20B82C1F5C for ; Fri, 15 Jan 2016 13:22:39 +0000 (UTC) Date: Fri, 15 Jan 2016 13:22:39 +0000 (UTC) From: "Andriy Redko (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CXF-6740) Collision by Swagger2Feature in two OSGI bundles MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-6740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15101755#comment-15101755 ] Andriy Redko edited comment on CXF-6740 at 1/15/16 1:22 PM: ------------------------------------------------------------ This is very interesting issue, apparently related to changes in Swagger 2. So what is happing, and you see that as well, /cxf/bpc-core/swagger.json and /cxf/bpc-monitor/swagger.json return the same results. However, you should see 2 tags in the resulting json, something like: {code} "tags": [ { "name": "bpc-core" }, { "name": "bpc-monitor" } ] {code} Very luckily, the heavy use of statics in Swagger may cause this weird behaviour. I will try to investigate if something could be done in CXF to workaround that. Thank you. was (Author: reta): This is very interesting issue, apparently related to changes in Swagger 2. So what is happing, and you see that as well, /cxf/bpc-core/swagger.json and /cxf/bpc-monitor/swagger.json return the same results. However, you should see 2 tags in the resulting json, something like: {code} "tags": [ { "name": "bpc-core" }, { "name": "bpc-monitor" } ] {code} Apparently, the heavy use of statics in Swagger may cause this weird behaviour. I will try to investigate if something could be done in CXF to workaround that. Thank you. > Collision by Swagger2Feature in two OSGI bundles > ------------------------------------------------- > > Key: CXF-6740 > URL: https://issues.apache.org/jira/browse/CXF-6740 > Project: CXF > Issue Type: Bug > Components: OSGi > Affects Versions: 3.1.4 > Environment: Apache Karaf 4.0.2 > Reporter: Andre Schlegel > Assignee: Andriy Redko > > I have two separate bundles in my karaf, which are using cxf with the swagger2feature. The endpoints (/cxf/bpc-core and /cxf/bpc-monitor/ ) in both bundles working fine. But I got on both swagger-URL the same swagger-File (both for the monitor endpoints). > I'm using the blueprint for swagger2feature configuration and annotation for the endpoints. > core bundle > {code} > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:cxf="http://cxf.apache.org/blueprint/core" > xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs" > xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd > http://cxf.apache.org/blueprint/core http://cxf.apache.org/schemas/blueprint/core.xsd > http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/blueprint/jaxrs.xsd"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > {code} > Monitor Bundle > {code} > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:cxf="http://cxf.apache.org/blueprint/core" > xmlns:jaxrs="http://cxf.apache.org/blueprint/jaxrs" > xsi:schemaLocation="http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd > http://cxf.apache.org/blueprint/core http://cxf.apache.org/schemas/blueprint/core.xsd > http://cxf.apache.org/jaxrs http://cxf.apache.org/schemas/blueprint/jaxrs.xsd"> > > > > > > > Center"/> > > > > > > > > > > > > > > > > > > > > {code} > I got the swagger-file for the monitor bundle on /cxf/bpc-core/swagger.json and /cxf/bpc-monitor/swagger.json > Anyone suggestion how to handle this scenario? -- This message was sent by Atlassian JIRA (v6.3.4#6332)