This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/activemq-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new e6e497401 Automatic Site Publish by Buildbot
e6e497401 is described below
commit e6e4974014b4813b6a1cf3c70c70f93be10e18d6
Author: buildbot <[email protected]>
AuthorDate: Fri May 9 21:12:38 2025 +0000
Automatic Site Publish by Buildbot
---
output/components/classic/documentation/jms2.html | 58 +++++++++++------------
output/index.html | 4 +-
2 files changed, 30 insertions(+), 32 deletions(-)
diff --git a/output/components/classic/documentation/jms2.html
b/output/components/classic/documentation/jms2.html
index 1f437a841..47cdcba1a 100644
--- a/output/components/classic/documentation/jms2.html
+++ b/output/components/classic/documentation/jms2.html
@@ -87,15 +87,13 @@
<div class="content">
<div class="page-title-classic">
<div class="container">
- <h1>JMS v2.0</h1>
+ <h1>ActiveMQ Classic Jakarta Messaging 3.1 & JMS 2.0 Support</h1>
</div>
</div>
<div class="container" >
<div class="row" style="margin-top: 30px">
<div class="col-12 classic">
- <p><a href="connectivity">Connectivity</a> > <a
href="protocols">Protocols</a> > <a href="jms2">JMS 2.0</a></p>
-
-<p>ActiveMQ Classic 5.x support for JMS v3.1 and v2.0 is in progress.</p>
+ <p><strong>ActiveMQ Classic 5.x & 6.x support for Jakarta
Messaging 3.1 & JMS 2.0 is in progress</strong>. If you need full support
for Jakarta Messaging 3.1 or JMS 2.0 we recommend <a
href="/components/artemis">ActiveMQ Artemis</a>.</p>
<h3 id="transition-approach">Transition Approach</h3>
@@ -103,7 +101,7 @@
<p>As features are implemented in subsequent releases, these exceptions will
be replaced with fully functional methods, examples and unit tests. See
later/below for more details on implementation progress.</p>
-<h3 id="jakarta-messaging-31-support">Jakarta Messaging 3.1 support</h3>
+<h3 id="jakarta-messaging">Jakarta Messaging</h3>
<p>Support for JMS 2.0 also enables building upon this for transition to
Jakarta Messaging 3.1 and its new <code class="language-plaintext
highlighter-rouge">jakarta.jms</code> API namespace rather than the historical
<code class="language-plaintext highlighter-rouge">javax.jms</code>
namespace.</p>
@@ -129,21 +127,21 @@
<tbody>
<tr>
<td>activemq-client</td>
- <td>jakarta.jms</td>
+ <td><code class="language-plaintext
highlighter-rouge">jakarta.jms</code></td>
<td>6.0.x</td>
- <td>Jakarta Messaging 3.1 support. Works with embedded broker and VM
transport.</td>
+ <td>Partial Jakarta Messaging 3.1 support. Works with embedded broker
and VM transport.</td>
</tr>
<tr>
<td>activemq-client</td>
- <td>javax.jms</td>
+ <td><code class="language-plaintext
highlighter-rouge">javax.jms</code></td>
<td>5.18.x</td>
- <td>JMS 2.0 support. Works with embedded broker and VM transport.</td>
+ <td>Partial JMS 2.0 support. Works with embedded broker and VM
transport.</td>
</tr>
<tr>
<td>activemq-client-jakarta</td>
- <td>jakarta.jms</td>
+ <td><code class="language-plaintext
highlighter-rouge">jakarta.jms</code></td>
<td>5.18.1+</td>
- <td>Transitional module for initial <em>client-only</em> Jakarta
Messaging 3.1 support. Can’t be used in the same JVM as activemq-client or
broker which use javax.jms API. <strong>Note this means no embedded broker / VM
transport support, only remote brokers.</strong></td>
+ <td>Transitional module for partial, <em>client-only</em> Jakarta
Messaging 3.1 support. Can’t be used in the same JVM as activemq-client or
broker which use javax.jms API. <strong>Note this means no embedded broker / VM
transport support, only remote brokers.</strong></td>
</tr>
</tbody>
</table>
@@ -165,16 +163,16 @@
<span class="nt"><version></span>${activemq.version}<span
class="nt"></version></span>
<span class="nt"></dependency></span>
</code></pre></div></div>
-<p>Note: With ActiveMQ Classic 6.0, the <code class="language-plaintext
highlighter-rouge">activemq-client-jakarta</code> module is removed as it is no
longer needed.</p>
+<p>Note: With ActiveMQ Classic 6.x the <code class="language-plaintext
highlighter-rouge">activemq-client-jakarta</code> module is removed as it is no
longer needed.</p>
<h3 id="spring-bean-usage">Spring bean usage</h3>
<p>Spring bean definitions do not change for Jakarta support.</p>
<div class="language-xml highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><span class="nt"><bean</span> <span
class="na">class=</span><span
class="s">"org.apache.activemq.ActiveMQConnectionFactory"</span><span
class="nt">></span>
</code></pre></div></div>
-<h3 id="activemq-classic-jms-v31-v20-implementation-progress">ActiveMQ Classic
JMS v3.1, v2.0 Implementation Progress</h3>
+<h3 id="implementation-progress">Implementation Progress</h3>
-<p>The implementation approach is subject to change. Be sure to verify
features in Release notes.</p>
+<p>The implementation approach is subject to change. Be sure to verify
features in release notes.</p>
<p>User feedback is welcome! Please comment on the JIRAs with questions and
comments.</p>
@@ -182,7 +180,7 @@
<thead>
<tr>
<th>JIRA</th>
- <th>Status</th>
+ <th style="text-align: center">Status</th>
<th>Target Version</th>
<th>Completed Version</th>
<th>Feature</th>
@@ -192,7 +190,7 @@
<tbody>
<tr>
<td><a
href="https://issues.apache.org/jira/browse/AMQ-7309";>AMQ-7309</a></td>
- <td>merged</td>
+ <td style="text-align: center">✅</td>
<td>5.18.0</td>
<td>5.18.0</td>
<td>JMS v2.0 API dependency</td>
@@ -200,7 +198,7 @@
</tr>
<tr>
<td><a
href="https://issues.apache.org/jira/browse/AMQ-8322";>AMQ-8322</a></td>
- <td>merged</td>
+ <td style="text-align: center">✅</td>
<td>5.18.0</td>
<td>5.18.0</td>
<td>JMSContext</td>
@@ -208,7 +206,7 @@
</tr>
<tr>
<td><a
href="https://issues.apache.org/jira/browse/AMQ-8322";>AMQ-8322</a></td>
- <td>merged</td>
+ <td style="text-align: center">✅</td>
<td>5.18.0</td>
<td>5.18.0</td>
<td>JMSRuntimeException</td>
@@ -216,7 +214,7 @@
</tr>
<tr>
<td><a
href="https://issues.apache.org/jira/browse/AMQ-8322";>AMQ-8322</a></td>
- <td>merged</td>
+ <td style="text-align: center">✅</td>
<td>5.18.0</td>
<td>5.18.0</td>
<td>JMSConsumer</td>
@@ -224,7 +222,7 @@
</tr>
<tr>
<td><a
href="https://issues.apache.org/jira/browse/AMQ-8322";>AMQ-8322</a></td>
- <td>merged</td>
+ <td style="text-align: center">✅</td>
<td>5.18.0</td>
<td>5.18.0</td>
<td>JMSProducer</td>
@@ -232,7 +230,7 @@
</tr>
<tr>
<td><a
href="https://issues.apache.org/jira/browse/AMQ-8321";>AMQ-8321</a></td>
- <td>merged</td>
+ <td style="text-align: center">✅</td>
<td>5.18.0</td>
<td>5.18.0</td>
<td>GetBody/isBodyAssignable</td>
@@ -240,7 +238,7 @@
</tr>
<tr>
<td><a
href="https://issues.apache.org/jira/browse/AMQ-8325";>AMQ-8325</a></td>
- <td>merged</td>
+ <td style="text-align: center">✅</td>
<td>6.0.0, 5.18.3</td>
<td>6.0.0, 5.18.3</td>
<td>XA Connection methods</td>
@@ -248,32 +246,32 @@
</tr>
<tr>
<td><a
href="https://issues.apache.org/jira/browse/AMQ-8464";>AMQ-8464</a></td>
- <td>PR <a
href="https://github.com/apache/activemq/pull/1046";>#1046</a></td>
- <td>6.1.0, 5.18.4</td>
+ <td style="text-align: center">❌</td>
+ <td>6.2.0</td>
<td> </td>
<td>JMSConsumer</td>
- <td>.receiveBody(Class<T>) methods</T></td>
+ <td><code class="language-plaintext
highlighter-rouge">.receiveBody(Class<T>)</code> methods</td>
</tr>
<tr>
<td><a
href="https://issues.apache.org/jira/browse/AMQ-8320";>AMQ-8320</a></td>
- <td>PR <a
href="https://github.com/apache/activemq/pull/982";>#982</a></td>
- <td>6.1.0, 5.18.4</td>
+ <td style="text-align: center">❌</td>
+ <td>6.2.0</td>
<td> </td>
<td>Delivery Delay</td>
<td>Support for Message DeliveryDelay feature</td>
</tr>
<tr>
<td><a
href="https://issues.apache.org/jira/browse/AMQ-8324";>AMQ-8324</a></td>
- <td>PR <a
href="https://github.com/apache/activemq/pull/1045";>#1045</a></td>
- <td>6.1.0, 5.18.4</td>
+ <td style="text-align: center">❌</td>
+ <td>6.2.0</td>
<td> </td>
<td>JMSProducer features</td>
<td>Completion Listener async send support</td>
</tr>
<tr>
<td><a
href="https://issues.apache.org/jira/browse/AMQ-8323";>AMQ-8323</a></td>
+ <td style="text-align: center">❌</td>
<td> </td>
- <td>6.2.0, 5.18.5</td>
<td> </td>
<td>Shared Topic Consumer</td>
<td>Multi-consumer (queue-like) consuming from topic subscriptions</td>
diff --git a/output/index.html b/output/index.html
index aa504eaf2..0162cfb96 100644
--- a/output/index.html
+++ b/output/index.html
@@ -177,7 +177,7 @@
<h4 class="card-title text-pink">ActiveMQ Classic</h4>
<p>Long established, endlessly pluggable architecture serving many
generations of applications.</p>
<ul>
- <li>Jakarta Messaging 3.1, JMS 2.0, and JMS 1.1 with full client
implementation including JNDI</li>
+ <li><a href="/components/classic/documentation/jms2">Partial Jakarta
Messaging 3.1 & JMS 2.0 support</a> and full JMS 1.1 support + full client
implementation including JNDI</li>
<li>High availability using shared storage</li>
<li>Familiar JMS-based addressing model</li>
<li>Network of brokers for distributing load</li>
@@ -194,7 +194,7 @@
<h4 class="card-title text-purple">ActiveMQ Artemis</h4>
<p>High-performance, non-blocking architecture for the next generation
of messaging applications.</p>
<ul>
- <li>JMS 1.1 & 2.0 + Jakarta Messaging 2.0 & 3.0 with full
client implementations including JNDI</li>
+ <li>Full Jakarta Messaging 3.1, JMS 2.0 & 1.1 support + full
client implementations including JNDI</li>
<li>High availability using shared storage or network
replication</li>
<li>Simple & powerful protocol agnostic addressing model</li>
<li>Flexible clustering for distributing load</li>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
