You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by "J. Fiala" <mo...@fwd.at> on 2016/11/18 18:28:54 UTC
Microservice multipe version support in single WAR-file / multiple
Swagger2Feature-Beans
Dear Sergey,
To implement multiple version support in one WAR file I'd need to have
two Swagger2Feature-beans, one with resourcePackage-filtering for
com.foo.myapp.v1 and another for com.foo.myapp.v2.
(basically the idea is to support multiple versions at the server side
but provide separate consistent contracts to the client so they don't
have to worry which version to use).
I defined two Swagger2Feature-Beans and they work if I activate them
separately. However having two Swagger2Feature beans both will simply
show everything without the resourcePackage-filtering working (the
version attribute itself will display correctly).
Maybe it makes sense to setup a separate sample for this, as
breaking-api versioning problem has been addressed in a few talks
@ApacheCon.
I can provide the currently not working sample if you like for more
analysis.
Best regards,
Johannes
Re: Microservice multipe version support in single WAR-file /
multiple Swagger2Feature-Beans
Posted by Sergey Beryozkin <sb...@gmail.com>.
Hi
Have a look at a description_swagger2_web demo please
Cheers, Sergey
On 18/11/16 18:28, J. Fiala wrote:
> Dear Sergey,
>
> To implement multiple version support in one WAR file I'd need to have
> two Swagger2Feature-beans, one with resourcePackage-filtering for
> com.foo.myapp.v1 and another for com.foo.myapp.v2.
>
> (basically the idea is to support multiple versions at the server side
> but provide separate consistent contracts to the client so they don't
> have to worry which version to use).
>
> I defined two Swagger2Feature-Beans and they work if I activate them
> separately. However having two Swagger2Feature beans both will simply
> show everything without the resourcePackage-filtering working (the
> version attribute itself will display correctly).
>
> Maybe it makes sense to setup a separate sample for this, as
> breaking-api versioning problem has been addressed in a few talks
> @ApacheCon.
> I can provide the currently not working sample if you like for more
> analysis.
>
> Best regards,
> Johannes
>
--
Sergey Beryozkin
Talend Community Coders
http://coders.talend.com/