CAMEL-23526: docs - flag camel-cxf 4.14 upgrade-guide entry as potential breaking change#23462
Merged
Merged
Conversation
…ial breaking change Signed-off-by: Andrea Cosentino <ancosen@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Flags the
camel-cxfentry incamel-4x-upgrade-guide-4_14.adocas a potentialbreaking change, matching the existing
camel-grok - potential breaking changeconvention. The CXF Exchange-header constant rename (CAMEL-23526, shipped on
this line via #23376) changes header values and alters cross-transport
propagation — a behaviour change worth flagging in the section title so readers
scanning the guide notice it.
Docs-only; no code change.
JIRA: https://issues.apache.org/jira/browse/CAMEL-23526
PR prepared by Claude Code on behalf of Andrea Cosentino.