This is an automated email from the ASF dual-hosted git repository.

oscerd pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new ed5ccd6689ed chore(docs): sync 4.18 and 4.14 upgrade guides with 
camel-sjms entry (#22988)
ed5ccd6689ed is described below

commit ed5ccd6689edf22de436089064f2b8bc70dd4e33
Author: Andrea Cosentino <[email protected]>
AuthorDate: Wed May 6 10:29:56 2026 +0200

    chore(docs): sync 4.18 and 4.14 upgrade guides with camel-sjms entry 
(#22988)
    
    Follow-up to #22969. CAMEL-23409 (camel-sjms - Disable ObjectMessage by
    default) was backported to camel-4.18.x via #22968 and to camel-4.14.x
    via #22970, both of which updated the upgrade guides on their respective
    maintenance branches but not the per-version files on main.
    
    Add the missing === camel-sjms / camel-sjms2 entry to:
    
    - camel-4x-upgrade-guide-4_18.adoc (under "Upgrading from 4.18.1 to 4.18.3")
    - camel-4x-upgrade-guide-4_14.adoc (under "Upgrading from 4.14.3 to 4.14.8")
    
    Placed between the existing camel-jms and camel-hazelcast entries so the
    two JMS-related notes sit together. Per the project's "Backport
    upgrade-guide policy" rule (codified in #22969 and the OSS rule pack),
    this keeps main's per-version upgrade guides in sync with what shipped
    on the maintenance branches.
    
    Signed-off-by: Andrea Cosentino <[email protected]>
---
 .../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc    | 28 ++++++++++++++++++++++
 .../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc    | 28 ++++++++++++++++++++++
 2 files changed, 56 insertions(+)

diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
index 09654549927d..dfab1bd1be37 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
@@ -45,6 +45,34 @@ Or, on a single endpoint:
 jms:queue:foo?objectMessageEnabled=true
 ----
 
+=== camel-sjms / camel-sjms2
+
+The same default applies to `camel-sjms` (and `camel-sjms2`, which inherits 
from it): JMS `ObjectMessage`
+support is now disabled by default and gated by a new `objectMessageEnabled` 
option (default `false`)
+on `SjmsComponent` / `SjmsEndpoint`.
+
+This affects the same endpoint/component options as `camel-jms`:
+
+* `jmsMessageType=Object` (or sending a `Serializable` body that is 
auto-detected as `Object`)
+* `transferException=true`
+* receiving a JMS `ObjectMessage` produced by an external sender
+
+To restore the previous behavior, enable the option at the component or 
endpoint level:
+
+[source,properties]
+----
+camel.component.sjms.objectMessageEnabled=true
+camel.component.sjms2.objectMessageEnabled=true
+----
+
+Or, on a single endpoint:
+
+[source,text]
+----
+sjms:queue:foo?objectMessageEnabled=true
+sjms2:queue:foo?objectMessageEnabled=true
+----
+
 === camel-hazelcast
 
 Hazelcast instances created and managed by Camel (when no user-supplied
diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index f503a01901c3..afe73be91679 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -45,6 +45,34 @@ Or, on a single endpoint:
 jms:queue:foo?objectMessageEnabled=true
 ----
 
+=== camel-sjms / camel-sjms2
+
+The same default applies to `camel-sjms` (and `camel-sjms2`, which inherits 
from it): JMS `ObjectMessage`
+support is now disabled by default and gated by a new `objectMessageEnabled` 
option (default `false`)
+on `SjmsComponent` / `SjmsEndpoint`.
+
+This affects the same endpoint/component options as `camel-jms`:
+
+* `jmsMessageType=Object` (or sending a `Serializable` body that is 
auto-detected as `Object`)
+* `transferException=true`
+* receiving a JMS `ObjectMessage` produced by an external sender
+
+To restore the previous behavior, enable the option at the component or 
endpoint level:
+
+[source,properties]
+----
+camel.component.sjms.objectMessageEnabled=true
+camel.component.sjms2.objectMessageEnabled=true
+----
+
+Or, on a single endpoint:
+
+[source,text]
+----
+sjms:queue:foo?objectMessageEnabled=true
+sjms2:queue:foo?objectMessageEnabled=true
+----
+
 === camel-hazelcast
 
 Hazelcast instances created and managed by Camel (when no user-supplied

Reply via email to