Re: Swagger2feature / 3.1.12 (DOSGI)

Hi Thanks for the confirmation, 3.2.1 will probably be available in central next week Sergey On 27/10/17 06:01, nino martinez wael wrote: I think my IDE cached exactly that dependency.. I can confirm that you guard/fix are working :) Do you know when 3.2.1 will be released? regards Nino

Re: Swagger2feature / 3.1.12 (DOSGI)

Hi Sergey I just reforked the master branch (after commit 3b4ed05b1217040ead101fb14c0441d41241f32d ), apparently I failed doing so.. I will try 3.1.14-SNAPSHOT instead.. On 26 Oct 2017 16:20, "Sergey Beryozkin" wrote: > As I said, I've added a check there, try

Re: Swagger2feature / 3.1.12 (DOSGI)

As I said, I've added a check there, try 3.1.14-SNAPSHOT Sergey On 26/10/17 13:09, nino martinez wael wrote: okay, I have what are happening.. First call are spring that sets the host property.. Immediately after this, the following happens: AbstractSwaggerFeature.initialize:67 are being

Re: Swagger2feature / 3.1.12 (DOSGI)

Hi again I've been stepping through the code, and something are definitely wrong. All other properties set in the app context xml have been processed and set in the swagger 2 feature and are acting logical.. BUT the HOST property are 0.0.0.0:9000 on initialization.. Which seems strange, I'll

Re: Swagger2feature / 3.1.12 (DOSGI)

Thanks, sure, I've added a guard there to avoid auto-setting the host value if it's not null, you can try 3.1.14-SNAPSHOT or 3.2.1-SNAPSHOT now. However, the question remains where '0.0.0.0' comes from in your case, when no host is set, which is a typical scenario, and I can see it is reported

Re: Swagger2feature / 3.1.12 (DOSGI)

Hmm... I may've been wrong with some of the assumptions about what Swagger2Feature does. Can you please do a breakpoint at https://github.com/apache/cxf/blob/cxf-3.1.12/rt/rs/description-swagger/src/main/java/org/apache/cxf/jaxrs/swagger/AbstractSwaggerFeature.java#L103 and see what happens,

Re: Swagger2feature / 3.1.12 (DOSGI)

Hi CXF does not contribute itself to the generation of 'host' within the Swagger JSON. For example, try a jaxrs/spring-boot demo, or some of other swagger2 demos... If you'd like you can get the CXF source, and step through the CXF Swagger2Feature Sergey On 12/10/17 11:06, nino martinez

Re: Swagger2feature / 3.1.12 (DOSGI)

In this case it is really somewhere in the Swagger code Sergey On 11/10/17 18:29, nino martinez wael wrote: No problem, I tried both configurations but no matter what I do, the host remains the same 0.0.0.0:9090 On 11 Oct 2017 15:51, "Sergey Beryozkin"

Re: Swagger2feature / 3.1.12 (DOSGI)

No problem, I tried both configurations but no matter what I do, the host remains the same 0.0.0.0:9090 On 11 Oct 2017 15:51, "Sergey Beryozkin" wrote: Sorry, I accidentally moved it from the users list, On 11/10/17 14:42, nino martinez wael wrote: > Sure, in my example

Re: Swagger2feature / 3.1.12 (DOSGI)

Sorry, I accidentally moved it from the users list, On 11/10/17 14:42, nino martinez wael wrote: Sure, in my example you can see that host 0.0.0.0:9090 have been generated.. However calling http://0.0.0.0:9090/tdc/dialer/webservices/v1/fullcampaigns

Re: Swagger2feature / 3.1.12 (DOSGI)

Im not sure if I have explained myself correctly.. The problem is this: http://localhost:9090/tdc/dialer/webservices/v1/swagger.json#/ { "swagger" : "2.0", "info" : { "description" : "Osgi Dialer Webservice", "version" : "1.26.0.SNAPSHOT", "title" : "Osgi Dialer Webservice",

Swagger2feature / 3.1.12 (DOSGI)

Hi I am running a dedicated CXF JAX RS on 0.0.0.0:9090 the issue are that my swagger.json states that the host are 0.0.0.0:9090 I've tried to overwrite it using: Swagger2Feature swagger = new Swagger2Feature(); swagger.setHost("127.0.0.1:9000"); But swagger.json remains unchanged. What am I