[
https://issues.jboss.org/browse/WFLY-12313?page=com.atlassian.jira.plugin...
]
Paul Ferraro commented on WFLY-12313:
-------------------------------------
[~michael.edgar] {quote}With that change, it would mean that there may be multiple
`/openapi` contexts registered depending on the number of servers and virtual hosts the
application(s) define, correct?{quote}
Yes. In an extreme example, each application within an EAR could be configured to use
different undertow servers, and thus might be accessed by distinct listeners, listening on
different network interfaces. In this scenario, we would want the /openapi context for
each app to be registered with the relevant server/host.
{quote}I researched this a bit and it looks like the server/virtual host names can be
retrieved from `JBossWebMetaData` if they have been configured. Otherwise, it would be
necessary to get them from `UndertowService`. Is that the way you are suggesting?{quote}
It's probably easiest to obtain this information from the DeploymentInfo [1] service
(see [2]) , which is installed during the Phase.INSTALL_WAR_DEPLOYMENT. Otherwise,
you'd need to work out the default values yourself.
[1]
https://github.com/undertow-io/undertow/blob/master/servlet/src/main/java...
[2]
https://github.com/wildfly/wildfly/blob/master/undertow/src/main/java/org...
Implement MP OpenAPI
--------------------
Key: WFLY-12313
URL:
https://issues.jboss.org/browse/WFLY-12313
Project: WildFly
Issue Type: Feature Request
Reporter: Michael Edgar
Assignee: Paul Ferraro
Priority: Major
Please integrate MicroProfile OpenAPI.
Details about MP OpenAPI:
https://github.com/eclipse/microprofile-open-api/releases/tag/1.1.2
Maybe it is possible to use SmallRye implementation:
https://github.com/smallrye/smallrye-open-api
--
This message was sent by Atlassian Jira
(v7.13.8#713008)