[
https://issues.apache.org/jira/browse/CXF-8115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16929439#comment-16929439
]
Andriy Redko edited comment on CXF-8115 at 9/13/19 6:32 PM:
------------------------------------------------------------
Hi [~Arnaud Roubinet], this used to be a know issue with Swagger
([https://github.com/OAI/OpenAPI-Specification/issues/146),] as far as I know,
you cannot define identical methods which differ by headers (but you could do
this in one method, using @Produces / @Consumes). Thank you.
was (Author: reta):
Hi [~Arnaud Roubinet], this used to be a know issue with Swagger
([https://github.com/OAI/OpenAPI-Specification/issues/146),] as far I know, you
cannot define identical methods which differ by headers (but you could do this
in one method, using @Produces / @Consumes). Thank you.
> OpenApiFeature dosn't allow the versioning by media type
> --------------------------------------------------------
>
> Key: CXF-8115
> URL: https://issues.apache.org/jira/browse/CXF-8115
> Project: CXF
> Issue Type: Bug
> Components: JAX-RS
> Affects Versions: 3.4.0
> Reporter: Arnaud Roubinet
> Priority: Major
> Labels: openapi
> Attachments: image-2019-09-13-14-59-08-362.png,
> image-2019-09-13-15-02-00-815.png, spring_boot.zip
>
>
> With open api 3.0, one of the new features allow using media type for
> versioning our api. (Instead of using the path)
>
> When exposing operations with same HTTP verb and path, but different media
> type (Consume or produce), we expected the generated swagger to provide both
> in the description.
> Unfortunately, only one appear in the generated document which is a
> limitation of open api 2.0.
> At this point I don’t know if I should open a bug or a new feature task.
>
> I will provide an example base on the demo projet.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
