More then one content type of response

Q	A
Bug or feature request?	Bug
Which Swagger-Core version?	2.0.0-rc1
Which Java version?	Java-8
Which JAX-RS framework & version?	Jackson 2.9.1, Jersey 2.25.1

Hi,

I have an endpoint like above and I want to have more than one content type of response. As I see in the openAPI specification it is possible but using annotation I can’n generate it.

@POST
    @Operation(summary = "Create multilevel query execution", responses = {
            @ApiResponse(responseCode = "200",
                    content = @Content(mediaType = "application/multiLevel+json", 
                            schema = @Schema(implementation = MultiLevelResult.class))),
            @ApiResponse(responseCode = "200",
                    content = @Content(mediaType = "application/flat+json",
                            schema = @Schema(implementation = FlatResult.class))),
            @ApiResponse(responseCode = "500", description = "An unexpected error has occurred. Error code is unexpected.error")})
    @Consumes({"application/execution.multiLevelQuery+json"})
    @Produces({"application/flat+json", "application/multiLevel+json"})

As result of the generation, I get only one content type.

"paths" : {
    "/queryExecutions" : {
      "post" : {
        "summary" : "Create multilevel query execution",
        "operationId" : "executeQuery",
        "parameters" : [ {
          "schema" : {
            "$ref" : "#/components/schemas/ClientMultiLevelQueryExecution"
          }
        } ],
        "responses" : {
          "200" : {
            "content" : {
              "application/flatData+json" : {
                "schema" : {
                  "$ref" : "#/components/schemas/ClientFlatQueryResultData"
                }
              }
            }
          },
          "500" : {
            "description" : "An unexpected error has occurred. Error code is unexpected.error"
          }
        }
      }
    }
  }

Does it not implemented yet?

[jameslaneconkling]

Is there at least a suggested path forward while this is not supported? For cases where there are multiple resources (e.g. getAsJSON and getAsCSV), I had thought it would work to decorate one with multiple @Content annotations for each mime type, and leave the other unannotated. However, it looks like the order in which each resource is parsed is non-deterministic, so if the annotated resource is evaluated second, the correct docs are produced, but if the unannotated resource is evaluated second, it overwrites the annotated resource and the docs are lost.

I’m fishing around for the least hacky way to solve this, given that there doesn’t seem much interest in supporting the use case. Is there a way to ignore a resource method? The only way I can think of doing this is to put annotated resources in a different package from unannotated ones.

[flo-ryan]

Any update on this? It seems that API accept header versioning is not possible with Swagger at the moment?