Swagger versus paths versus service registration

[Benson Margulies <be...@basistech.com>]

We've structured a service as a collection of microservices. Each one
separately creates itself as a RESTful service on the same port by
calling the usual CXF API.

As as result, none of the resource classes have interesting @Path
annotations, since the path that distinguishes them is part of the API
call to CXF.

We managed to get this to work, more or less, with Swagger 1.x. We
want to move to Swagger 2 to solve some other problems.

Has anyone else had to work with this shape/pattern in Swagger 2?

Re: Swagger versus paths versus service registration

[Sergey Beryozkin <sb...@gmail.com>]

Hi Benson

let us know if you see some specific issues, may be Swagger2 feature can 
be tuned somehow, etc

Cheers, Sergey

On 19/04/16 13:37, Benson Margulies wrote:
> We've structured a service as a collection of microservices. Each one
> separately creates itself as a RESTful service on the same port by
> calling the usual CXF API.
>
> As as result, none of the resource classes have interesting @Path
> annotations, since the path that distinguishes them is part of the API
> call to CXF.
>
> We managed to get this to work, more or less, with Swagger 1.x. We
> want to move to Swagger 2 to solve some other problems.
>
> Has anyone else had to work with this shape/pattern in Swagger 2?
>


-- 
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/