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 ec5fd1959 Automatic Site Publish by Buildbot
ec5fd1959 is described below
commit ec5fd19596e7427b245f5775bde9861304b70803
Author: buildbot <[email protected]>
AuthorDate: Mon Mar 27 14:01:41 2023 +0000
Automatic Site Publish by Buildbot
---
output/activemq-5018000-release.html | 2 +-
output/index.html | 2 +-
output/jms2.html | 44 ++++++++++++++++++------------------
output/news/index.html | 2 +-
4 files changed, 25 insertions(+), 25 deletions(-)
diff --git a/output/activemq-5018000-release.html
b/output/activemq-5018000-release.html
index f33e14a1c..7b5c93ae8 100644
--- a/output/activemq-5018000-release.html
+++ b/output/activemq-5018000-release.html
@@ -100,7 +100,7 @@
<p>Apache ActiveMQ 5.18.0 was released on Mar 24th, 2023. It’s a major
milestone for the ActiveMQ project.
ActiveMQ 5.18.x brings:</p>
<ul>
- <li>JMS2 compliant clients, with one client using javax.jms namespacee and
one clieent using jakarta.jms namespace (see <a href="/jms2">JMS v2.0
page</a>)</li>
+ <li>It brings initial JMS 2.0 (javax.jms API namespace) and Jakarta
Messaging 3.1 (jakarta.jms API namespace) client support. See the <a
href="/jms2">JMS 2.0 page</a> for more details on the available functionality
and how to use the Jakarta Messaging support.</li>
<li>Spring 5.3.x</li>
<li>optimized LDAP use in LDAP JAAS login module</li>
<li>improved REST API</li>
diff --git a/output/index.html b/output/index.html
index 3aa4097b3..0faed51b8 100644
--- a/output/index.html
+++ b/output/index.html
@@ -127,7 +127,7 @@
- 5.18.0 is an important milestone, starting the new 5.18.x series. It
brings JMS2 clients (both javax and jakarta namespaces), Spring 5.3.x, a bunch
of dependency updates, and a lot of fixes and improvements.<a style="display:
unset;" class="nav-link pl-0 ml-0" href="/activemq-5018000-release">...more</a>
+ 5.18.0 is an important milestone. It brings initial JMS 2.0 (javax.jms API
namespace) and Jakarta Messaging 3.1 (jakarta.jms API namespace) client
support, Spring 5.3.x, a bunch of dependency updates, and a lot of fixes and
improvements.<a style="display: unset;" class="nav-link pl-0 ml-0"
href="/activemq-5018000-release">...more</a>
<p class="small text-muted text-right font-italic mb-0">Mar 24th, 2023</p>
</div>
diff --git a/output/jms2.html b/output/jms2.html
index 84f036048..c227253ab 100644
--- a/output/jms2.html
+++ b/output/jms2.html
@@ -100,18 +100,18 @@
<h3 id="transition-approach">Transition Approach</h3>
-<p>Initially, ActiveMQ Clients will throw an UnsupportedOperationException
(RuntimeException) for JMS v2.0 methods and features. This ensures that
existing JMS v2.0 frameworks are notified of the coming JMS v2.0 support for
ActiveMQ and have time to accomodate the changes accordingly.</p>
+<p>Initially, ActiveMQ clients will not support all JMS 2.0 functionality and
will throw an UnsupportedOperationException (RuntimeException) for unsupported
methods and features, such as those for async send with a CompletionListener,
sending messages with a delivery delay, and using shared topic consumers.</p>
-<p>As features are implemented in subsequent releases, these exceptions will
be replaced with fully functional methods, examples and unit tests.</p>
+<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-support">Jakarta support</h3>
+<h3 id="jakarta-messaging-31-support">Jakarta Messaging 3.1 support</h3>
-<p>Support for JMS 2.0 will also enable the transition to the Jakarta
namespace.</p>
+<p>The initial support for JMS 2.0 also enables building upon this for
transition to Jakarta Messaging 3.1 and its new jakarta.jms API namespace
rather than the historical javax.jms namespace.</p>
<ul>
<li>The standard for Java Enterprise features going forward</li>
<li>Required for Spring 6</li>
- <li>Required for Jakarta EE</li>
+ <li>Required for Jakarta EE 9 + 10.</li>
<li>JMS API Java package name-change only</li>
<li>ActiveMQ package names do not change</li>
</ul>
@@ -122,7 +122,7 @@
<thead>
<tr>
<th>Client jar</th>
- <th>JMS Package</th>
+ <th>API Package</th>
<th>Version</th>
<th>Notes</th>
</tr>
@@ -138,7 +138,7 @@
<td>activemq-client-jakarta</td>
<td>jakarta.jms</td>
<td>5.18.0</td>
- <td>Transitional module for client-only Jakarta support</td>
+ <td>Transitional module for client-only Jakarta support. Can not be used
in the same JVM as javax.jms activemq-client or broker.</td>
</tr>
</tbody>
</table>
@@ -229,14 +229,6 @@ import jakarta.jms...
<td>JMSProducer</td>
<td>Produce messages</td>
</tr>
- <tr>
- <td><a
href="https://issues.apache.org/jira/browse/AMQ-8320";>AMQ-8320</a></td>
- <td> </td>
- <td>5.18.1</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-8321";>AMQ-8321</a></td>
<td>merged</td>
@@ -246,20 +238,20 @@ import jakarta.jms...
<td>Support for checking body type using a Class<?></td>
</tr>
<tr>
- <td><a
href="https://issues.apache.org/jira/browse/AMQ-8324";>AMQ-8324</a></td>
+ <td><a
href="https://issues.apache.org/jira/browse/AMQ-8320";>AMQ-8320</a></td>
<td> </td>
<td>5.18.1</td>
<td> </td>
- <td>JMSProducer features</td>
- <td>Completion Listener and Delivery Delay support</td>
+ <td>Delivery Delay</td>
+ <td>Support for Message DeliveryDelay feature</td>
</tr>
<tr>
- <td><a
href="https://issues.apache.org/jira/browse/AMQ-8325";>AMQ-8325</a></td>
+ <td><a
href="https://issues.apache.org/jira/browse/AMQ-8324";>AMQ-8324</a></td>
<td> </td>
- <td>TBD</td>
+ <td>5.18.1</td>
<td> </td>
- <td>XA Connection methods</td>
- <td>Updated methods when using XA Transactions</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>
@@ -269,6 +261,14 @@ import jakarta.jms...
<td>Shared Topic Consumer</td>
<td>Multi-consumer (queue-like) consuming from topic subscriptions</td>
</tr>
+ <tr>
+ <td><a
href="https://issues.apache.org/jira/browse/AMQ-8325";>AMQ-8325</a></td>
+ <td> </td>
+ <td>TBD</td>
+ <td> </td>
+ <td>XA Connection methods</td>
+ <td>Updated methods when using XA Transactions</td>
+ </tr>
</tbody>
</table>
diff --git a/output/news/index.html b/output/news/index.html
index 03e48cf90..6e49982be 100644
--- a/output/news/index.html
+++ b/output/news/index.html
@@ -97,7 +97,7 @@
<h3 id="activemq-5180-release">ActiveMQ 5.18.0 Release</h3>
<p><span class="text-secondary"> Mar 24th, 2023</span></p>
-<p>5.18.0 is an important milestone, starting the new 5.18.x series. It brings
JMS2 clients (both javax and jakarta namespaces), Spring 5.3.x, a bunch of
dependency updates, and a lot of fixes and improvements.</p>
+<p>5.18.0 is an important milestone. It brings initial JMS 2.0 (javax.jms API
namespace) and Jakarta Messaging 3.1 (jakarta.jms API namespace) client
support, Spring 5.3.x, a bunch of dependency updates, and a lot of fixes and
improvements.</p>
<p><a href="/activemq-5018000-release">Read More</a></p>
