#24303 Fix more links

Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>

docs/application-deployment-guide/src/main/asciidoc/deploying-applications.adoc

@@ -1324,7 +1324,7 @@ module. Redeployment of a connector module results in the shared class
 loader reloading the new classes. Other modules that refer to the old
 resource adapter classes must be redeployed to gain access to the new
 classes. For more information about class loaders, see
-"link:application-development-guide/class-loaders.html#class-loaders[Class Loaders]" in {productName} Application Development Guide.
+"xref:application-development-guide.adoc#class-loaders[Class Loaders]" in {productName} Application Development Guide.
 
 During connector module redeployment, the server log provides a warning
 indicating that all dependent applications should be redeployed. Client
@@ -1439,7 +1439,7 @@ For more detailed information about the `appclient` script, see
 xref:reference-manual.adoc#appclient[`appclient`(1M)].
 
 For more detailed information about creating application clients, see
-"link:application-development-guide/java-clients.html#developing-java-clients[Developing Java Clients]" in {productName} Application Development Guide. This chapter includes
+"xref:application-development-guide.adoc#developing-java-clients[Developing Java Clients]" in {productName} Application Development Guide. This chapter includes
 information on the following topics:
 
 * Accessing EJB components and JMS resources from application clients
@@ -1547,7 +1547,7 @@ module interfaces are in the as-install``/modules/glassfish-api.jar``
 file.
 
 For general information about lifecycle modules, see
-"link:application-development-guide/lifecycle-listeners.html#developing-lifecycle-listeners[Developing Lifecycle Listeners]" in {productName} Application Development Guide.
+"xref:application-development-guide.adoc#developing-lifecycle-listeners[Developing Lifecycle Listeners]" in {productName} Application Development Guide.
 
 You can deploy a lifecycle module using the `create-lifecycle-module`
 subcommand. Do not use `asadmin deploy` or related commands.
@@ -1601,7 +1601,7 @@ click the Web Service component. The table in the right frame lists
 deployed web service endpoints.
 
 For more information about web services, see
-"link:application-development-guide/webservices.html#developing-web-services[Developing Web Services]" in {productName} Application Development Guide.
+"xref:application-development-guide.adoc#developing-web-services[Developing Web Services]" in {productName} Application Development Guide.
 
 [[osgi-bundle-deployment-guidelines]]
 

docs/application-deployment-guide/src/main/asciidoc/overview.adoc

@@ -112,7 +112,7 @@ production environment.
 For production environments, any upgrade should be performed as a
 rolling upgrade, which upgrades applications and modules without
 interruption in service. For more information, see
-link:ha-administration-guide/rolling-upgrade.html#upgrading-applications-without-loss-of-availability[Upgrading Applications Without Loss of Availability] in
+xref:ha-administration-guide.adoc#upgrading-applications-without-loss-of-availability[Upgrading Applications Without Loss of Availability] in
 {productName} High Availability Administration
 Guide.
 
@@ -265,7 +265,7 @@ format for assembling connector modules. Each {productName} connector
 has annotations or a deployment descriptor file (`ra.xml`).
 +
 After deploying a J2EE connector module, you must configure it as
-described in link:application-development-guide/connectors.html#developing-connectors[Developing Connectors] in {productName} Application Development Guide.
+described in xref:application-development-guide.adoc#developing-connectors[Developing Connectors] in {productName} Application Development Guide.
 * Application Client Module. An application client module is a
 deployable software unit that consists of one or more classes, and
 application client deployment descriptors (`application-client.xml` and
@@ -274,7 +274,7 @@ applies to a {productName} type of Jakarta EE client. An application
 client supports the standard Jakarta EE Application Client specifications.
 * Lifecycle Module. A lifecycle module provides a means of running
 short-duration or long-duration Java-based tasks within the {productName} environment. Lifecycle modules are not Jakarta EE standard modules.
-See link:application-development-guide/lifecycle-listeners.html#developing-lifecycle-listeners[Developing Lifecycle Listeners] in {productName} Application Development Guide for more information.
+See xref:application-development-guide.adoc#developing-lifecycle-listeners[Developing Lifecycle Listeners] in {productName} Application Development Guide for more information.
 
 [[module-based-deployment]]
 
@@ -339,7 +339,7 @@ remove the libraries with `remove-library`. For more information about
 all these commands, see the {productName}
 Reference Manual.
 
-For more information about class loaders, see link:application-development-guide/class-loaders.html#class-loaders[Class
+For more information about class loaders, see xref:application-development-guide.adoc#class-loaders[Class
 Loaders] in {productName} Application Development
 Guide.
 

docs/application-development-guide/src/main/asciidoc/ejb.adoc

@@ -922,7 +922,7 @@ Read-only beans have the following characteristics:
 (CMP) is allowed. If CMP is used, do not create the database schema
 during deployment. Instead, work with your database administrator to
 populate the data into the tables. See
-link:container_managed-persistence.html#using-container-managed-persistence[Using Container-Managed
+xref:container_managed-persistence.adoc#using-container-managed-persistence[Using Container-Managed
 Persistence].
 * Only container-managed transactions are allowed; read-only beans
 cannot start their own transactions.