eclipse-ee4j#24303 Fix link:GXXXXXX links

Signed-off-by:Ondro Mihalyi <mihalyi@omnifish.ee>
OndroMih · Feb 21, 2023 · acc29c2 · acc29c2
1 parent 65a96d6
commit acc29c2
Show file tree

Hide file tree

Showing 11 changed files with 16 additions and 16 deletions.
diff --git a/...on-component-development-guide/src/main/asciidoc/adding-configuration-data.adoc b/...on-component-development-guide/src/main/asciidoc/adding-configuration-data.adoc
@@ -647,7 +647,7 @@ import org.jvnet.hk2.config.TransactionFailure;
 === Dotted Names and REST URLs of Configuration Attributes
 
 The {productName} administrative subcommands link:reference-manual/get.html#get[`get`],
-link:reference-manual/list.html#list[`list`], and link:GSRFM00226[`set`] locate a
+link:reference-manual/list.html#list[`list`], and xref:reference-manual.adoc#set[`set`] locate a
 configuration attribute through the dotted name of the attribute. The
 dotted name of an attribute of a configuration element is as follows:
 

diff --git a/...mponent-development-guide/src/main/asciidoc/adding-monitoring-capabilities.adoc b/...mponent-development-guide/src/main/asciidoc/adding-monitoring-capabilities.adoc
@@ -414,7 +414,7 @@ To enable system administrators to access statistics for all components
 in the same way, you must provide statistics for an add-on component by
 updating the monitorable object tree. Statistics for the add-on
 component are then available through the {productName} administrative
-commands link:reference-manual/get.html#get[`get`], link:GSRFM00145[`list`], and
+commands link:reference-manual/get.html#get[`get`], xref:reference-manual.adoc#list[`list`], and
 link:reference-manual/set.html#set[`set`]. These commands locate an object in the tree
 through the object's dotted name.
 
@@ -803,7 +803,7 @@ public class TransactionManagerImpl {
 === Dotted Names and REST URLs for an Add-On Component's Statistics
 
 The {productName} administrative subcommands link:reference-manual/get.html#get[`get`],
-link:reference-manual/list.html#list[`list`], and link:GSRFM00226[`set`] locate a statistic
+link:reference-manual/list.html#list[`list`], and xref:reference-manual.adoc#set[`set`] locate a statistic
 through the dotted name of the statistic. The dotted name of a statistic
 for an add-on component is determined from the registration of the event
 listener that defines the statistic as follows:

diff --git a/docs/administration-guide/src/main/asciidoc/general-administration.adoc b/docs/administration-guide/src/main/asciidoc/general-administration.adoc
@@ -1299,7 +1299,7 @@ Each `POST` method and `DELETE` method that a REST resource supports has
 an equivalent `asadmin` subcommand. The parameters of a `POST` method or
 a `DELETE` method correspond to the options of the method's equivalent
 `asadmin` subcommand. For information about the options of `asadmin`
-subcommand, see the link:GSRFM[{productName}
+subcommand, see the xref:reference-manual.adoc[{productName}
 Reference Manual].
 ====
 

diff --git a/docs/administration-guide/src/main/asciidoc/jdbc.adoc b/docs/administration-guide/src/main/asciidoc/jdbc.adoc
@@ -459,7 +459,7 @@ for the pool, and restores the pool to its steady pool size.
 
 1. Ensure that the server is running. Remote subcommands require a running server.
 2. Reset a connection pool by using
-the link:GSRFM00135[`flush-connection-pool`] subcommand.
+the xref:reference-manual.adoc#flush-connection-pool[`flush-connection-pool`] subcommand.
 
 [[gjirk]]
 Example 11-6 Resetting (Flushing) a Connection Pool

diff --git a/docs/administration-guide/src/main/asciidoc/jndi.adoc b/docs/administration-guide/src/main/asciidoc/jndi.adoc
@@ -348,7 +348,7 @@ existing JNDI resources.
 
 1. Ensure that the server is running. Remote subcommands require a running server.
 2. List the existing JNDI resources by using
-the link:GSRFM00179[`list-jndi-resources`] subcommand.
+the xref:reference-manual.adoc#list-jndi-resources[`list-jndi-resources`] subcommand.
 
 [[giwbe]]
 Example 18-6 Listing JNDI Resources
@@ -405,7 +405,7 @@ typing `asadmin help list-jndi-entries` at the command line.
 ===== To Update an External JNDI Resource
 
 1. List the existing JNDI resources by using
-the link:GSRFM00179[`list-jndi-resources`] subcommand.
+the xref:reference-manual.adoc#list-jndi-resources[`list-jndi-resources`] subcommand.
 2. Use the link:reference-manual/set.html#set[`set`] subcommand to modify an external
 JNDI resource.
 

diff --git a/docs/administration-guide/src/main/asciidoc/lifecycle-modules.adoc b/docs/administration-guide/src/main/asciidoc/lifecycle-modules.adoc
@@ -159,7 +159,7 @@ applications.application.sampleLCMmodule.property.classpath=/build/lcm.jar
 applications.application.sampleLCMmodule.property.is-failure-fatal=false
 applications.application.sampleLCMmodule.property.isLifecycle=true
 ----
-2. Update a life cycle module by using the link:GSRFM00226[`set`]
+2. Update a life cycle module by using the xref:reference-manual.adoc#set[`set`]
 subcommand.
 3. Restart the server for your changes to take effect.
 +

diff --git a/docs/administration-guide/src/main/asciidoc/overview.adoc b/docs/administration-guide/src/main/asciidoc/overview.adoc
@@ -603,7 +603,7 @@ To avoid this situation, do one of the following:
 * Enable secure admin so that what {productName} interprets as a
 remote request is accepted as such.
 
-To enable secure admin, see "link:GSSCG00039[Managing Administrative
+To enable secure admin, see "xref:security-guide.adoc#managing-administrative-security[Managing Administrative
 Security]" in {productName} Security Guide.
 ====
 

diff --git a/docs/application-deployment-guide/src/main/asciidoc/dd-elements.adoc b/docs/application-deployment-guide/src/main/asciidoc/dd-elements.adoc
@@ -8781,7 +8781,7 @@ connection factories.
 When `resource-ref` specifies a JMS connection factory for the Open
 Message Queue, the `default-resource-principal` (name/password) must
 exist in the Message Queue user repository. Refer to the Security
-Management chapter in the link:GMADG[Open Message Queue Administration
+Management chapter in the xref:{mq-admin-guide-url}[Open Message Queue Administration
 Guide] for information on how to manage the Message Queue user
 repository.
 ====

diff --git a/docs/application-development-guide/src/main/asciidoc/ejb.adoc b/docs/application-development-guide/src/main/asciidoc/ejb.adoc
@@ -357,7 +357,7 @@ deploying applications that will use the timer.
 Do not use the `jdbc/\__TimerPool` resource for timers in clustered
 {productName} environments.
 You must instead use a custom JDBC resource or the `jdbc/__default` resource.
-See "link:GSADG00747[Enabling the jdbc/__default Resource in a Clustered Environment]"
+See "xref:administration-guide.adoc#etjdbcdefault-cluster[Enabling the jdbc/__default Resource in a Clustered Environment]"
 in {productName} Administration Guide.
 ====
 
@@ -1192,7 +1192,7 @@ select the Monitor tab.
 ====
 Running monitoring when it is not needed might impact performance, so
 you might choose to turn monitoring off when it is not in use. For
-details, see "link:GSADG00011[Administering the Monitoring Service]" in
+details, see "xref:administration-guide.adoc#administering-the-monitoring-service[Administering the Monitoring Service]" in
 {productName} Administration Guide.
 ====
 

diff --git a/docs/ha-administration-guide/src/main/asciidoc/nodes.adoc b/docs/ha-administration-guide/src/main/asciidoc/nodes.adoc
@@ -310,7 +310,7 @@ following sections.
 ----
 asadmin> list-nodes-dcom --long=true
 ----
-3. Run the link:GSRFM00100[`delete-node-dcom`] subcommand.
+3. Run the xref:reference-manual.adoc#delete-node-dcom[`delete-node-dcom`] subcommand.
 +
 [source]
 ----
@@ -612,7 +612,7 @@ following sections.
 ----
 asadmin> list-nodes-ssh --long=true
 ----
-3. Run the link:GSRFM00100[`delete-node-ssh`] subcommand.
+3. Run the xref:reference-manual.adoc#delete-node-dcom[`delete-node-ssh`] subcommand.
 +
 [source]
 ----
@@ -837,7 +837,7 @@ Instance Locally].
 ----
 asadmin> list-nodes-config --long=true
 ----
-3. Run the link:GSRFM00099[`delete-node-config`] subcommand.
+3. Run the xref:reference-manual.adoc#delete-node-config[`delete-node-config`] subcommand.
 +
 [source]
 ----

diff --git a/...ha-administration-guide/src/main/asciidoc/session-persistence-and-failover.adoc b/...ha-administration-guide/src/main/asciidoc/session-persistence-and-failover.adoc
@@ -242,7 +242,7 @@ them by using the following command for each instance:
 asadmin> start-instance instance-name
 ----
 
-4. Use one of the following `asadmin` link:GSRFM00226[`set`]
+4. Use one of the following `asadmin` xref:reference-manual.adoc#set[`set`]
 subcommands to enable availability for a specific cluster, or for a
 specific Web, EJB, or JMS container.
 * For a cluster as a whole