This is an automated email from the ASF dual-hosted git repository.
robbie pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/activemq-website.git
The following commit(s) were added to refs/heads/main by this push:
new 905ea8e04 update release and status pages to clarify JMS 2.0 and
Jakarta Messsagig 3.1 distinction, make clearer what is/isnt supported yet +
how to use latter, more directly note the same-JVM considerations"
905ea8e04 is described below
commit 905ea8e04ca34c4d9c18984a128686fbad48d5de
Author: Robbie Gemmell <[email protected]>
AuthorDate: Mon Mar 27 13:46:10 2023 +0100
update release and status pages to clarify JMS 2.0 and Jakarta Messsagig
3.1 distinction, make clearer what is/isnt supported yet + how to use latter,
more directly note the same-JVM considerations"
---
src/_5x_releases/activemq-5018000-release.md | 4 ++--
src/jms2.md | 20 ++++++++++----------
2 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/src/_5x_releases/activemq-5018000-release.md
b/src/_5x_releases/activemq-5018000-release.md
index 6f16a1c11..53c8b5b4b 100644
--- a/src/_5x_releases/activemq-5018000-release.md
+++ b/src/_5x_releases/activemq-5018000-release.md
@@ -4,11 +4,11 @@ release_notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=
release_date: 2023-03-24
title: ActiveMQ 5.18.0 Release
java_version: 11+
-shortDescription: 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.
+shortDescription: 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.
---
Apache ActiveMQ {{ page.version }} was released on {{ page.release_date |
date_to_string: "ordinal", "US" }}. It's a major milestone for the ActiveMQ
project.
ActiveMQ 5.18.x brings:
-* JMS2 compliant clients, with one client using javax.jms namespacee and one
clieent using jakarta.jms namespace (see [JMS v2.0 page](/jms2))
+* It brings initial JMS 2.0 (javax.jms API namespace) and Jakarta Messaging
3.1 (jakarta.jms API namespace) client support. See the [JMS 2.0 page](/jms2)
for more details on the available functionality and how to use the Jakarta
Messaging support.
* Spring 5.3.x
* optimized LDAP use in LDAP JAAS login module
* improved REST API
diff --git a/src/jms2.md b/src/jms2.md
index c3ccfaba8..ecfb83276 100644
--- a/src/jms2.md
+++ b/src/jms2.md
@@ -13,26 +13,26 @@ Adding support for JMS v2.0 creates compatability
challenges both for existing J
### Transition Approach
-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.
+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.
-As features are implemented in subsequent releases, these exceptions will be
replaced with fully functional methods, examples and unit tests.
+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.
-### Jakarta support
+### Jakarta Messaging 3.1 support
-Support for JMS 2.0 will also enable the transition to the Jakarta namespace.
+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.
* The standard for Java Enterprise features going forward
* Required for Spring 6
- * Required for Jakarta EE
+ * Required for Jakarta EE 9 + 10.
* JMS API Java package name-change only
* ActiveMQ package names do not change
This allows for a dependency-update-only approach to the transition without
having to re-code going forward!
-Client jar|JMS Package|Version|Notes
+Client jar|API Package|Version|Notes
---|---|---
activemq-client | javax.jms | 5.18.0 |
-activemq-client-jakarta | jakarta.jms | 5.18.0 | Transitional module for
client-only Jakarta support
+activemq-client-jakarta | jakarta.jms | 5.18.0 | Transitional module for
client-only Jakarta support. Can not be used in the same JVM as javax.jms
activemq-client or broker.
There is no functional change, this is purely a Java package naming change:
@@ -71,11 +71,11 @@ JIRA|Status|Target Version|Completed Version|Feature|Notes
[AMQ-8322](https://issues.apache.org/jira/browse/AMQ-8322) | merged | 5.18.0 |
5.18.0 | JMSRuntimeException | Convert JMSExceptions to be JMSRuntimeExceptions
[AMQ-8322](https://issues.apache.org/jira/browse/AMQ-8322) | merged | 5.18.0 |
5.18.0 | JMSConsumer | Consume messages
[AMQ-8322](https://issues.apache.org/jira/browse/AMQ-8322) | merged | 5.18.0 |
5.18.0 | JMSProducer | Produce messages
-[AMQ-8320](https://issues.apache.org/jira/browse/AMQ-8320) | | 5.18.1 | |
Delivery Delay | Support for Message DeliveryDelay feature
[AMQ-8321](https://issues.apache.org/jira/browse/AMQ-8321) | merged | 5.18.0 |
5.18.0 | GetBody/isBodyAssignable | Support for checking body type using a
Class<?>
-[AMQ-8324](https://issues.apache.org/jira/browse/AMQ-8324) | | 5.18.1 | |
JMSProducer features | Completion Listener and Delivery Delay support
-[AMQ-8325](https://issues.apache.org/jira/browse/AMQ-8325) | | TBD | | XA
Connection methods | Updated methods when using XA Transactions
+[AMQ-8320](https://issues.apache.org/jira/browse/AMQ-8320) | | 5.18.1 | |
Delivery Delay | Support for Message DeliveryDelay feature
+[AMQ-8324](https://issues.apache.org/jira/browse/AMQ-8324) | | 5.18.1 | |
JMSProducer features | Completion Listener async send support
[AMQ-8323](https://issues.apache.org/jira/browse/AMQ-8323) | | TBD | | Shared
Topic Consumer | Multi-consumer (queue-like) consuming from topic subscriptions
+[AMQ-8325](https://issues.apache.org/jira/browse/AMQ-8325) | | TBD | | XA
Connection methods | Updated methods when using XA Transactions
### Feature notes
