Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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", ...)`).
Loading