Do you see some errors in the log for your own OSGI setup? That will tell something about the cause.
If not, I think we need to find out why the scanning is not correctly taking place in your own OSGi setup compared to the karaf setup using the same sample bundle. Either using remote debugging to directly compare the steps going into the scanning or activating the logger for io.swagger to compare the log results. regards, aki 2015-10-16 16:35 GMT+02:00 matteo <[email protected]>: > Hi Andrei, > Thank you for providing me with the cxf+swagger example coordinates. I tried > to load my endpoint bundle in Karaf with the OSGi runtime generated by the > /description_swagger2_osgi/ sample project feature file and swagger works > correctly: it produces the expected json descriptor for the endpoint! > On the other way around, if I deploy the > /org.apache.cxf.samples.jax_rs_description_swagger2_osgi/ demo bundle in my > original OSGi environment, it shows the same problem as my REST API bundle. > > So I think there must be some sort of difference between in the OSGi runtime > I used outside karaf and the OSGi runtime generated by karaf. Honestly, I > cannot spot any significant difference: they seem absolutely equal one to > the other; this is the runtime I used outside karaf (I put the bundles in > alphabetical order): > > and this is the karaf runtime generated in the /description_swagger2_osgi/ > (I put the bundles in alphabetical order and I removed the > org.apache.karaf.* bundles): > > Assuming bundle starting order does not matter, I cannot understand what is > the culprit in the first environment. Maybe some vm properties? What do you > think? > > Thanks again, > matteo > > > > ----- > matteo > -- > View this message in context: > http://cxf.547215.n5.nabble.com/Swagger2Feature-via-blueprint-config-does-not-produce-the-expected-results-tp5761841p5761943.html > Sent from the cxf-user mailing list archive at Nabble.com.
