Michael Edgar

Hi @matus-m , what is the use case for separately parsing a stand-alone schema? Do you have it in its own file and you want to add it to the...

Thanks for the information. We will be sure to not change the availability of `OpenApiParser#parseSchema` until there is a suitable replacement, and keep this issue open until then as well.

This seems like a reasonable feature to include. @t1 any time/interest in contributing a PR for this?

How about something like this? ```java @XmlRootElement(name = "foo") static class FooSchema { } @APIResponse(responseCode = "200", description = "Bla bla", content = { @Content(mediaType = MediaType.APPLICATION_JSON, example = "JSON...

Right, I agree. It seems to be more an issue with Swagger UI in my opinion. I'd expect it to perhaps be aware of the representation for the XML media...

> By this I mean that it's clear from the MediaType that it's XML, so the plugin could generate what's necessary to get it right. Unfortunately, just from the `@Content`...

Do you already have a class that represents the XML that includes `@XmlRootElement`? The `@Schema` annotation doesn't include a way to specify XML information, but it has been requested in...

@BrianSetz I suspect this may be a bug with Swagger UI not handling the `type: [ string, "null" ]` in OAS 3.1.0. Can you try it with an OAS 3.0.x...

As far as I can tell, this is because Swagger UI is only supporting a string value [1] for `type` (not an array as is the result in OAS 3.1...

@fabiobrz , yes I think it does. It appears from a quick look through the code that it's simply not handled at all for cases where it is placed on...