I am using cxf 3.1.9, I Downloaded demo from trunk, it is working (tags generated) will check farther, thanks
2017-01-12 17:06 GMT+04:00 Sergey Beryozkin <[email protected]>: > Hi > > Which CXF version do you use ? And do you mean "multiple JAXRS endpoints" > or a single endpoint with multiple root resources ? > Both options work in CXF demos (ex, jax_rs/spring_boot) and > description_swagger2_web > > Sergey > > On 12/01/17 08:55, Vjacheslav V. Borisov wrote: > >> Hi! >> >> Experimenting with javascript client generation based on swagger2feature >> generated swagger.json >> and noticed, that operations from all jax-rs resources placed on one >> "default" client >> so if different resources contains same method, there will be conflict. >> >> >> Looking at example here >> >> https://github.com/swagger-api/swagger-js ( source >> >> http://petstore.swagger.io/v2/swagger.json) >> >> client generation is split to three resources:pet, store, user >> >> This is also seen in swager-ui >> >> .../api-docs?/url=http://petstore.swagger.io/v2/swagger.json#/ >> >> This generation based on tags section >> "tags": [{ >> "name": "pet", >> "description": "Everything about your Pets", >> "externalDocs": { >> "description": "Find out more", >> "url": "http://swagger.io"; >> } >> }, { >> "name": "store", >> "description": "Access to Petstore orders" >> }, { >> "name": "user", >> "description": "Operations about user", >> "externalDocs": { >> "description": "Find out more about our store", >> "url": "http://swagger.io"; >> } >> }], >> >> And every method bound to tag >> >> Should swagger2feature also generate [tags] section based on number of >> root >> resources >> and link every method to one of root resources? >> >> > > -- > Sergey Beryozkin > > Talend Community Coders > http://coders.talend.com/ >
