[ https://issues.redhat.com/browse/WFLY-13638?page=com.atlassian.jira.plugi... ] Rhuan Rocha updated WFLY-13638: ------------------------------- Description: In the Wildfly 20, if I deploy two application in the same server just one registry an openapi endpoint. Look at this code: [https://github.com/wildfly/wildfly/blob/501c916b14663d328582a6625e9d492c2...]   It makes sense as the endpoint is registered to _http://\{host}:\{port}/openpi_, but I think it is better to registry it considering the context root. With this, we can registry multiples openapi per server. Thus the openapi endpoint can be registered to _http://\{host}:\{port}/\{context-root}/openapi._ Looking at the code looks like it is possible to be done. If we have access to the information of context-root in [https://github.com/wildfly/wildfly/blob/501c916b14663d328582a6625e9d4..., then we can start it in considering the context-root. I think it will be a very common scenario of use and it will be very helpful to users.  was: In the Wildfly 20, if I deploys two application in the same server just one registries an openapi endpoint. Look at this code: [https://github.com/wildfly/wildfly/blob/501c916b14663d328582a6625e9d492c2...]   It makes sense as the endpoint is registered to _http://\{host}:\{port}/openpi_, but I think it is better to registry it considering the context root. With this, we can registry multiples openapi per server. Thus the openapi endpoint can be registered to _http://\{host}:\{port}/\{context-root}/openapi._ Looking at the code looks like it is possible to be done. If we have access to the information of context-root in [https://github.com/wildfly/wildfly/blob/501c916b14663d328582a6625e9d4..., then we can start it in considering the context-root. I think it will be a very common scenario of use and it will be very helpful to users.  -- This message was sent by Atlassian Jira (v7.13.8#713008)