This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit b20430856f0179bb8d0985586b2e195b02dfff43
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Wed Jan 6 12:42:59 2021 +0100
CAMEL-15995: camel-sjms - Make it more feature compatible with camel-jms
(migrate)
---
.../modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git
a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc
b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc
index 3d7f27c..c8ca5f5 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc
@@ -10,6 +10,16 @@ from both 3.0 to 3.1 and 3.1 to 3.2.
The JMS and ActiveMQ component now supports optimized toD EIP pattern by using
a single endpoint/producer for dynamic destination names.
+=== camel-sjms and camel-sjms2
+
+These two components has been overhauled and re-written with the goals of
being more feature complete with the Spring JMS component.
+They also no longer uses their own connection pooling, but let you use the
existing 3rd party pooling for `ConnectionFactory` which is common practice.
+The components are now also reactive and non-blocking, and also supports
optimized toD EIP pattern by using a single endpoint/producer for dynamic
destination names.
+
+Many of the previous features and configuration options have been
removed/renamed.
+To migrate you need to read their documentation and see what options they now
offer.
+
+
=== Camel-AWS2-SNS
The policy option now expects a file, since the policy are going to be
complex. It can be from classpath:, http: or file: etc.
