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 b535bdfea057 CAMEL-23510: docs - sync camel-jgroups 4.14 upgrade-guide
entry to main (flagged as potential breaking change) (#23422)
b535bdfea057 is described below
commit b535bdfea0576184d73c126ba8fb0b2b855b717c
Author: Andrea Cosentino <[email protected]>
AuthorDate: Fri May 22 11:30:05 2026 +0200
CAMEL-23510: docs - sync camel-jgroups 4.14 upgrade-guide entry to main
(flagged as potential breaking change) (#23422)
* CAMEL-23510: sync 4.14 upgrade guide entry for jgroups header rename
PR #23209 added the JGroups header-rename note to the 4.21 upgrade
guide on main. The corresponding backport to camel-4.14.x adds an
equivalent entry to camel-4x-upgrade-guide-4_14.adoc on that
maintenance branch.
Per the upgrade-guide backport policy in CLAUDE.md, the same entry
must also be added to camel-4x-upgrade-guide-4_14.adoc on main so the
canonical history of the 4.14 release line on main stays in sync with
what ships on camel-4.14.x.
This commit only adds the camel-jgroups section under the existing
"Upgrading from 4.14.5 to 4.14.6" window, after the camel-cxf entry.
No code changes.
Signed-off-by: Andrea Cosentino <[email protected]>
* CAMEL-23510: flag camel-jgroups header rename as a potential breaking
change
Address @apupier's review comment: the JGroups header rename is a
breaking change for routes that read or write the headers by their
literal string value, so the upgrade-guide entry should say so
explicitly.
- Suffix the heading with " - potential breaking change" (matching the
=-= camel-grok - potential breaking change=- convention in the 4.21
guide).
- Lead the post-table prose with an explicit "This is a breaking change
for routes that ..." sentence.
Keeps this main-side 4.14 entry consistent with the equivalent wording
applied on camel-4.14.x (#23441) and on the 4.21 guide on main (#23451).
Signed-off-by: Andrea Cosentino <[email protected]>
---------
Signed-off-by: Andrea Cosentino <[email protected]>
---
.../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 22 ++++++++++++++++++++++
1 file changed, 22 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 4c4579f9ebf9..d15e27a9989e 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
@@ -441,3 +441,25 @@ between the transport `from` and the `cxf:` `to`:
The same pattern applies to HTTP-based bridges (`platform-http`/`jetty`/`netty
-http`/`http` -> `cxf:`) and any other transport whose default
`HeaderFilterStrategy` filters `Camel*` headers.
+
+=== camel-jgroups - potential breaking change
+
+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`
+|===
+
+This is a breaking change for routes that read or write these headers by
+their literal string value. 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", ...)`).
