Re: CXF 3.2.1 swagger generation are wrong for json

Yes I think so.. Although I have no proof it works on non osgi systems.. On Wed, 6 Dec 2017, 12:35 Sergey Beryozkin, wrote: > Hi Nino > > So it is a pure OSGI issue now, right ? > Lets ask Christian as well, Christian, can you advise how to overcome > this annotations

Re: CXF 3.2.1 swagger generation are wrong for json

Hi Nino So it is a pure OSGI issue now, right ? Lets ask Christian as well, Christian, can you advise how to overcome this annotations issue ? Cheers, Sergey On 06/12/17 11:30, nino martinez wael wrote: No change after getting the javax.xml.bind.annotation.. I can see I can change how some

Re: CXF 3.2.1 swagger generation are wrong for json

Okay after adding swagger annotations as an export from my bundle. The swagger json are now including whatever I describe in the annotations. However the maven bundle plugin keeps removing my export for javax.xml.bind.annotation and so I cannot test if this also have an impact on swagger ignoring

Re: CXF 3.2.1 swagger generation are wrong for json

I've started testing that idea, and it seems to have an impact.. I will return once I know more!! Thanks! On Mon, Dec 4, 2017 at 5:08 PM, Sergey Beryozkin wrote: > CXF Swagger feature itself is not importing Swagger annotations because it > does not work with them, I'm

Re: CXF 3.2.1 swagger generation are wrong for json

CXF Swagger feature itself is not importing Swagger annotations because it does not work with them, I'm not sure, may be you need to have your application bundle exporting the annotations to make the visible... Sergey On 04/12/17 15:06, nino martinez wael wrote: No, no namespaces And I

Re: CXF 3.2.1 swagger generation are wrong for json

No, no namespaces And I am still pussled on why it does not do it the "right" way.. Currently I am experimenting putting in io.swagger.annotations BUT they seem to have no effect on the generated swagger describtion when placed in our backend models, they are in another bundle, im wondering

Re: CXF 3.2.1 swagger generation are wrong for json

Nice, Just out of curiosity, what does Swagger set the XML Object's namespace to ? Is it initialized ? Sergey On 04/12/17 06:03, nino martinez wael wrote: Okay so I've looked into this a bit. And turned the problem upside down. Instead of trying to make the cxf swagger feature use jackson,

Re: CXF 3.2.1 swagger generation are wrong for json

Okay so I've looked into this a bit. And turned the problem upside down. Instead of trying to make the cxf swagger feature use jackson, just taking a look at the outcome and play around trying to change it.. Again if there is any way to see what the swagger feature plugin are using runtime to

Re: CXF 3.2.1 swagger generation are wrong for json

No change without setting swagger2customizer.. I'll let it rest for a day.. On Thu, Nov 30, 2017 at 1:30 PM, nino martinez wael < nino.martinez.w...@gmail.com> wrote: > yup have set skip.default.json.provider.registration.. > > But no matter what I do it has no effect on what the swagger

Re: CXF 3.2.1 swagger generation are wrong for json

yup have set skip.default.json.provider.registration.. But no matter what I do it has no effect on what the swagger feature generates.. Where it's changing the json provider or removing it all together.. Trying it now without setting swagger2Customizer.. On Thu, Nov 30, 2017 at 1:04 PM, Sergey

Re: CXF 3.2.1 swagger generation are wrong for json

It does not seem to be a jettison problem.. And neither an problem with jackson versions, I just wiped all jettison and jackson(except 2.9.1 ) versions from my running environment.. Looking into of it could be something with JacksonJaxbJsonProvider vs JacksonJsonProvider On Thu, Nov 30, 2017 at

Re: CXF 3.2.1 swagger generation are wrong for json

IS there somewhere while on runtime where I can print current registered providers for cxf, I have a feeling that it somehow are using jettison for json... On Thu, Nov 30, 2017 at 12:17 PM, nino martinez wael < nino.martinez.w...@gmail.com> wrote: > Okay I will check into libraries whats on

Re: CXF 3.2.1 swagger generation are wrong for json

Okay I will check into libraries whats on class path.. I have the same gut feeling that it could be something like that. I have enunciate up and working on the side.. On Thu, Nov 30, 2017 at 11:18 AM, Sergey Beryozkin wrote: > Yes, the minor Swagger version caused this

Re: CXF 3.2.1 swagger generation are wrong for json

Yes, the minor Swagger version caused this change, what was working 3.1.x, specifically the serializers approach, was not working any longer with the new Swagger version, hence this update. I honestly do not know why exactly a JAXB annotated bean is not correctly represented in the

Re: CXF 3.2.1 swagger generation are wrong for json

Okay I think something changed from cxf swagger 3.1.x to 3.2.x Earlier on I could specify this : DefaultSwagger2Serializers defaultSwagger2Serializers = new DefaultSwagger2Serializers(); defaultSwagger2Serializers.setJavadocProvider(new JavaDocProvider());

Re: CXF 3.2.1 swagger generation are wrong for json

Im wondering if this could be the problem : https://github.com/swagger-api/swagger-core/issues/960 On Thu, Nov 30, 2017 at 10:38 AM, nino martinez wael < nino.martinez.w...@gmail.com> wrote: > So I have a bean CXF accepts only this interpretation for my endpoint: > > { > "contactList": [ >

CXF 3.2.1 swagger generation are wrong for json

So I have a bean CXF accepts only this interpretation for my endpoint: { "contactList": [ { "campaignId": "2", "id":"", "indexNumber": "", "accountNumber": "232", "queueNumber": "0", "balance": 0,