Skip to content

[WFLY-20871] Correct the server version in the WildFly 37 docs #96

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Sep 17, 2025
Merged

[WFLY-20871] Correct the server version in the WildFly 37 docs #96

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
26 changes: 13 additions & 13 deletions 37/Admin_Guide.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -530,7 +530,7 @@ <h1>WildFly Admin Guide</h1>
<div class="details">
<span id="author" class="author">WildFly developer team</span><br>
<span id="revnumber">version 37.0.0.Final,</span>
<span id="revdate">2025-08-04T14:03:23Z</span>
<span id="revdate">2025-08-29T18:36:17Z</span>
</div>
<div id="toc" class="toc2">
<div id="toctitle">WildFly Admin guide</div>
Expand Down Expand Up @@ -1553,7 +1553,7 @@ <h4 id="operations"><a class="anchor" href="#operations"></a><a class="link" hre
</div>
<div class="paragraph">
<p>Every resource except the root resource will have an <code>add</code> operation and
should have a <code>remove</code> operation ("should" because in WildFly 36 many do
should have a <code>remove</code> operation ("should" because in WildFly 37 many do
not). The parameters for the <code>add</code> operation vary depending on the
resource. The <code>remove</code> operation has no parameters.</p>
</div>
Expand Down Expand Up @@ -7518,7 +7518,7 @@ <h3 id="DataSource"><a class="anchor" href="#DataSource"></a><a class="link" hre
<div class="sect3">
<h4 id="jdbc-driver-installation"><a class="anchor" href="#jdbc-driver-installation"></a><a class="link" href="#jdbc-driver-installation">7.3.1. JDBC Driver Installation</a></h4>
<div class="paragraph">
<p>The recommended way to install a JDBC driver into WildFly 36 is to deploy
<p>The recommended way to install a JDBC driver into WildFly 37 is to deploy
it as a regular JAR deployment. The reason for this is that when you run
WildFly in domain mode, deployments are automatically propagated to all
servers to which the deployment applies; thus distribution of the driver
Expand Down Expand Up @@ -13219,7 +13219,7 @@ <h4 id="cluster-authentication"><a class="anchor" href="#cluster-authentication"
<div class="sect3">
<h4 id="deployment-of--jms.xml-files"><a class="anchor" href="#deployment-of--jms.xml-files"></a><a class="link" href="#deployment-of--jms.xml-files">7.15.10. Deployment of -jms.xml files</a></h4>
<div class="paragraph">
<p>Starting with WildFly 36, you have the ability to deploy a -jms.xml file
<p>Starting with WildFly 37, you have the ability to deploy a -jms.xml file
defining Jakarta Messaging destinations, e.g.:</p>
</div>
<div class="listingblock">
Expand Down Expand Up @@ -13861,7 +13861,7 @@ <h4 id="Messaging_Backward_and_Forward_Compatibility"><a class="anchor" href="#M
</li>
<li>
<p>forward compatibility: legacy messaging clients (using HornetQ) can connect
to a WildFly 36 app server (running Artemis).</p>
to a WildFly 37 app server (running Artemis).</p>
</li>
</ul>
</div>
Expand Down Expand Up @@ -13914,7 +13914,7 @@ <h5 id="forward-compatibility"><a class="anchor" href="#forward-compatibility"><
</div>
<div class="paragraph">
<p>The <code>legacy-entries</code> must be used by legacy clients (using HornetQ)
while the regular <code>entries</code> are for WildFly 36 Jakarta Messaging clients (using
while the regular <code>entries</code> are for WildFly 37 Jakarta Messaging clients (using
Artemis).</p>
</div>
<div class="paragraph">
Expand All @@ -13936,7 +13936,7 @@ <h6 id="migration"><a class="anchor" href="#migration"></a><a class="link" href=
created with a <code>-new</code> suffix.<br>
If <code>add-legacy-entries</code> is set to <code>false</code> during migration, no legacy
resources will be created in the <code>messaging-activemq</code> subsystem and
legacy messaging clients will not be able to communicate with WildFly 36
legacy messaging clients will not be able to communicate with WildFly 37
servers.</p>
</div>
</div>
Expand All @@ -13946,7 +13946,7 @@ <h5 id="backward-compatibility"><a class="anchor" href="#backward-compatibility"
<div class="paragraph">
<p>Backward compatibility requires no configuration change in the legacy
server.<br>
WildFly 36 clients do not look up resources on the legacy server but
WildFly 37 clients do not look up resources on the legacy server but
use client-side JNDI to create their Jakarta Messaging resources. WildFly&#8217;s Artemis client
can then use these resources to communicate with the legacy server
using the HornetQ CORE protocol.</p>
Expand All @@ -13957,7 +13957,7 @@ <h5 id="backward-compatibility"><a class="anchor" href="#backward-compatibility"
JNDI</a> to create Jakarta Messaging resources ( <code>ConnectionFactory</code> and <code>Destination</code>).</p>
</div>
<div class="paragraph">
<p>For example, if a WildFly 36 messaging client wants to communicate with a
<p>For example, if a WildFly 37 messaging client wants to communicate with a
legacy server using a queue named <code>myQueue</code>, it must use the
following properties to configure its JNDI <code>InitialContext</code>:</p>
</div>
Expand Down Expand Up @@ -23877,7 +23877,7 @@ <h4 id="windows-and-press-any-key-to-continue-...-issue"><a class="anchor" href=
<div class="paragraph">
<p>To avoid "Press any key to continue &#8230;&#8203;" message you need to specify
NOPAUSE variable. Call 'set NOPAUSE=true' in command line before running
any WildFly 36 .bat script or include it in your custom script before
any WildFly 37 .bat script or include it in your custom script before
invoking scripts from WildFly.</p>
</div>
</div>
Expand Down Expand Up @@ -27169,7 +27169,7 @@ <h5 id="close-the-modelcontrollerclient"><a class="anchor" href="#close-the-mode
<div class="sect3">
<h4 id="format-of-a-detyped-operation-request"><a class="anchor" href="#format-of-a-detyped-operation-request"></a><a class="link" href="#format-of-a-detyped-operation-request">11.5.3. Format of a Detyped Operation Request</a></h4>
<div class="paragraph">
<p>The basic method a user of the WildFly 36 programmatic management API
<p>The basic method a user of the WildFly 37 programmatic management API
would use is very simple:</p>
</div>
<div class="listingblock">
Expand Down Expand Up @@ -27689,7 +27689,7 @@ <h6 id="creating-and-reusing-a-rollout-plan"><a class="anchor" href="#creating-a
<div class="sect3">
<h4 id="format-of-a-detyped-operation-response"><a class="anchor" href="#format-of-a-detyped-operation-response"></a><a class="link" href="#format-of-a-detyped-operation-response">11.5.4. Format of a Detyped Operation Response</a></h4>
<div class="paragraph">
<p>As noted previously, the basic method a user of the WildFly 36
<p>As noted previously, the basic method a user of the WildFly 37
programmatic management API would use is very simple:</p>
</div>
<div class="listingblock">
Expand Down Expand Up @@ -28277,7 +28277,7 @@ <h5 id="multi-server-responses"><a class="anchor" href="#multi-server-responses"
<div id="footer">
<div id="footer-text">
Version 37.0.0.Final<br>
Last updated 2025-07-14 17:03:31 -0500
Last updated 2025-07-14 18:03:31 -0400
</div>
</div>
</body>
Expand Down
Loading