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 bd0d0a049f3a CAMEL-23510: doc-sync 4.18 upgrade guide for 
camel-jgroups header rename
bd0d0a049f3a is described below

commit bd0d0a049f3a53ff36f03e84b637c7bdf55926a2
Author: Andrea Cosentino <[email protected]>
AuthorDate: Thu May 14 13:46:08 2026 +0200

    CAMEL-23510: doc-sync 4.18 upgrade guide for camel-jgroups header rename
    
    Doc-sync companion to backport #23213 (camel-jgroups header rename onto
    camel-4.18.x).
    
    Per the project's backport upgrade-guide policy, the
    camel-4x-upgrade-guide-4_XX.adoc files live only on main and act as the
    canonical history across all releases. This PR adds the camel-jgroups
    entry to camel-4x-upgrade-guide-4_18.adoc under the
    "Upgrading from 4.18.1 to 4.18.3" section, documenting the rename of
    the JGroups Exchange header string values to the CamelJGroups*
    convention.
    
    Closes #23219
---
 .../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc     | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

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 631494f8ed4a..4e0d816d6af4 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
@@ -109,6 +109,27 @@ Hazelcast topic, queue, map, list, set, or in one of the 
repositories
 above must provide their own `Config` with a
 `JavaSerializationFilterConfig` configured for their class names.
 
+=== camel-jgroups
+
+The Exchange header constants in `JGroupsConstants` have been renamed to follow
+the Camel naming convention used across the rest of the component catalog. The
+Java field names are unchanged; only the header string values have changed:
+
+[options="header"]
+|===
+| Constant | Previous value | New value
+| `JGroupsConstants.HEADER_JGROUPS_CHANNEL_ADDRESS` | 
`JGROUPS_CHANNEL_ADDRESS` | `CamelJGroupsChannelAddress`
+| `JGroupsConstants.HEADER_JGROUPS_DEST` | `JGROUPS_DEST` | `CamelJGroupsDest`
+| `JGroupsConstants.HEADER_JGROUPS_SRC` | `JGROUPS_SRC` | `CamelJGroupsSrc`
+| `JGroupsConstants.HEADER_JGROUPS_ORIGINAL_MESSAGE` | 
`JGROUPS_ORIGINAL_MESSAGE` | `CamelJGroupsOriginalMessage`
+|===
+
+Routes that reference the constant symbolically (for example
+`setHeader(JGroupsConstants.HEADER_JGROUPS_DEST, ...)`) continue to work
+without changes. Routes that set the header by its literal string value
+(for example `setHeader("JGROUPS_DEST", ...)`) must be updated to use the
+new value (`setHeader("CamelJGroupsDest", ...)`).
+
 == Upgrading from 4.18.0 to 4.18.1
 
 === camel-bom

Reply via email to