From b395778b07d4e1bd2db5b2927564e34a3c37081d Mon Sep 17 00:00:00 2001 From: Ramkumar K Date: Tue, 26 Nov 2024 12:28:33 +0530 Subject: [PATCH] 7654-Documentation-MicroProfile-OpenAPI-4.0-010 7654-Documentation-MicroProfile-OpenAPI-4.0-010 #7654 --- modules/ROOT/pages/documentation-openapi.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/documentation-openapi.adoc b/modules/ROOT/pages/documentation-openapi.adoc index 198be8388..558958ef0 100644 --- a/modules/ROOT/pages/documentation-openapi.adoc +++ b/modules/ROOT/pages/documentation-openapi.adoc @@ -198,7 +198,7 @@ MicroProfile Config provides properties to manage which applications and modules - When you configure support for multiple applications and multi-module environments by using MicroProfile Config, the application name is determined from the application's deployment descriptor (`application.xml` or `web.xml`). If the deployment descriptor is missing or does not specify a name, the application name defaults to the application archive file name without the file extension. Similarly, the module name is specified in the web module `web.xml` file. If the `web.xml` file does not exist or does not specify a name, the module name defaults to the file name without the file extension. - Any configuration that is defined in the `server.xml` file to include or exclude modules and applications takes precedence over configuration that is set through MicroProfile Config. + -For more information, see the xref:microprofile-config-properties.adoc#openap[MicroProfile Config properties for MicroProfile OpenAPI]. +For more information, see the xref:microprofile-config-properties.adoc#openapi[MicroProfile Config properties for MicroProfile OpenAPI]. == See also