This is an automated email from the ASF dual-hosted git repository.
oscerd pushed a commit to branch camel-4.14.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-4.14.x by this push:
new 3e797c0937fb CAMEL-23510: flag camel-jgroups header rename as
potential breaking change in 4.14 upgrade guide (#23441)
3e797c0937fb is described below
commit 3e797c0937fb1307a02614eaa8069b0c797a26cc
Author: Andrea Cosentino <[email protected]>
AuthorDate: Fri May 22 13:39:41 2026 +0200
CAMEL-23510: flag camel-jgroups header rename as potential breaking change
in 4.14 upgrade guide (#23441)
Follow-up to the camel-4.14.x backport #23421. Addresses @apupier's review
comment on #23422: the JGroups header constant rename is a breaking change
for routes that read or write the headers by their literal string value,
so the 4.14 upgrade-guide entry now says so explicitly.
- Heading suffixed with " - potential breaking change" (matching the
camel-grok convention).
- Prose leads with an explicit "This is a breaking change for routes that
..."
sentence.
Docs only; consistent with the same wording on the 4.14 guide on main
(#23422), the 4.18 guide (#23471) and the 4.21 guide (#23451).
---
.../modules/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 4198e3804d21..e5a5244c7184 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
@@ -453,7 +453,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
@@ -468,8 +468,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", ...)`).
