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 9d3395e10cbd CAMEL-23510: flag camel-jgroups header rename as
potential breaking change in 4.18 upgrade guide (#23471)
9d3395e10cbd is described below
commit 9d3395e10cbd699d3237033da1b3c1be7998a98b
Author: Andrea Cosentino <[email protected]>
AuthorDate: Fri May 22 13:39:51 2026 +0200
CAMEL-23510: flag camel-jgroups header rename as potential breaking change
in 4.18 upgrade guide (#23471)
Follow-up to #23209 completing the breaking-change labelling across all
affected upgrade guides. The JGroups header rename was backported to
camel-4.18.x (#23213) and documented on main's 4.18 guide via doc-sync
#23219, but that entry did not flag the rename as a breaking change.
- 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; identical wording to the 4.14 guide (#23422 / #23441) and the
4.21 guide (#23451).
---
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
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 300af5580bf8..f2a1f558a29d 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,7 +109,7 @@ 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
+=== 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
@@ -124,11 +124,12 @@ 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", ...)`).
=== camel-lucene
