[ https://issues.jboss.org/browse/TEIIDSB-62?page=com.atlassian.jira.plugin... ] Steven Hawkins edited comment on TEIIDSB-62 at 6/10/19 1:16 PM: ---------------------------------------------------------------- I think the ask was to not use anything with swagger in the url. Whether it's opeanapi, openapi.json, or openapi_v2.json shouldn't matter correct? Which is a small breaking change... So we can (updating based upon another thread): 1. just use openapi_v2.json for the 2.0 document. 2. follow microprofile and make /openapi require a json content type and return the 3.0 document by default (as per the spec). openapi v2 would be served by including some other header or query parameter value. was (Author: shawkins): I think the ask was to not use anything with swagger in the url. Whether it's opeanapi, openapi.json, or openapi_v2.json shouldn't matter correct? Which is a small breaking change... So we can: 1. follow microprofile and make /openapi require a json content type and return the 2.0 document. openapi.json would continue to server the 3.0 document. 2. just use openapi_v2.json for the 2.0 document. 3. reuse openapi.json for both 2 and 3 and specify what header we expect as the discriminator. I prefer the solutions in that order - 1 is based upon some reference. 2 is a very small code change. 3 is a small breaking change and requires the use of a non-standard header property. -- This message was sent by Atlassian Jira (v7.12.1#712002)