[ https://issues.apache.org/jira/browse/CXF-7117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15668455#comment-15668455 ]
Sergey Beryozkin commented on CXF-7117: --------------------------------------- Right, I see what you mean. Swagger just picks up everything and at least with a servlet based approach it can be dealt with. It is quite hard to control the Swagger behaviour, Swagger2Feature already does many tricks. Looks like one more is needed, surely Andriy will think of something :-) > Swagger2Feature not working in OSGi container when jaxrs server address not > attached to CXF servlet > --------------------------------------------------------------------------------------------------- > > Key: CXF-7117 > URL: https://issues.apache.org/jira/browse/CXF-7117 > Project: CXF > Issue Type: Bug > Components: OSGi > Affects Versions: 3.1.8 > Environment: Apache Karaf 3.0.8 > Reporter: Concombre Masqué > Assignee: Andriy Redko > > Just modify sample description_swagger2_osgi as follows: > <!-- CXF Swagger2Feature --> > <bean id="swagger2Feature" > class="org.apache.cxf.jaxrs.swagger.Swagger2Feature"> > <property name="basePath" value="/test/swaggerSample"/> > <property name="usePathBasedConfig" value="true" /> > </bean> > <cxf:bus> > <cxf:features> > <cxf:logging /> > </cxf:features> > </cxf:bus> > <jaxrs:server id="sampleServer" > address="http://localhost:9091/test/swaggerSample";> > <jaxrs:serviceBeans> > <ref component-id="sampleResource" /> > </jaxrs:serviceBeans> > <jaxrs:providers> > <ref component-id="jsonProvider" /> > <ref component-id="multipartProvider" /> > <ref component-id="originFilter" /> > </jaxrs:providers> > <jaxrs:features> > <ref component-id="swagger2Feature" /> > </jaxrs:features> > </jaxrs:server> > Then deploy modified bundle into Karaf and browse Swagger service definition > at http://localhost:9091/test/swaggerSample/swagger.json > Result is: > {"swagger":"2.0"} -- This message was sent by Atlassian JIRA (v6.3.4#6332)
