From 45044a8df3afee8f603ca21eb4723dbb29a8825b Mon Sep 17 00:00:00 2001 From: Andrea Cosentino Date: Thu, 21 May 2026 19:35:05 +0200 Subject: [PATCH] CAMEL-23510: flag camel-jgroups header rename as a potential breaking change in 4.14 upgrade guide PR #23421 backported the JGroups header constant rename to camel-4.14.x and added an upgrade-guide entry under "Upgrading from 4.14.5 to 4.14.6". @apupier pointed out on #23422 that the entry does not explicitly call out that the rename is a breaking change for routes that read or write these headers by their literal string value. Update the entry to: - Suffix the section heading with " - potential breaking change", which is the established convention in the upgrade guides (e.g. the =-= camel-grok - potential breaking change=- heading in the 4.21 guide). - Lead the post-table prose with an explicit "This is a breaking change for routes that ..." sentence, before the existing symbolic-vs-literal guidance. No code changes; docs only. Signed-off-by: Andrea Cosentino --- .../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) 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 954025c9c1dc7..d484427193cef 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 @@ -430,7 +430,7 @@ 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 +=== 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 @@ -445,8 +445,9 @@ Java field names are unchanged; only the header string values have changed: | `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", ...)`). +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", ...)`).