[backport camel-4.14.x] CAMEL-23515: camel-nats - Use dedicated HeaderFilterStrategy aligned with sibling components#23255
Open
oscerd wants to merge 1 commit into
Conversation
…with sibling components (apache#23233) Introduce NatsHeaderFilterStrategy following the KafkaHeaderFilterStrategy / MailHeaderFilterStrategy shape (lowerCase=true, filter headers starting with Camel/camel/org.apache.camel. in both directions), and switch the default in NatsConfiguration to use it. Signed-off-by: Andrea Cosentino <ancosen@gmail.com> (cherry picked from commit be8aad9)
davsclaus
approved these changes
May 15, 2026
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
2 participants
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.
Backport of #23233
Cherry-pick of #23233 onto
camel-4.14.x.Original PR: #23233 - CAMEL-23515: camel-nats - Use dedicated HeaderFilterStrategy aligned with sibling components
Original author: @oscerd
Target branch:
camel-4.14.xConflict resolution
NatsConfiguration.java: real merge conflict because the field orderingdiverged on
camel-4.14.x(JetStream fields sit directly afterheaderFilterStrategy). Resolved by keeping all the 4.14.x-specificsurrounding code and only swapping
new DefaultHeaderFilterStrategy()->new NatsHeaderFilterStrategy()(theDefaultHeaderFilterStrategyimportremoval applied cleanly;
NatsHeaderFilterStrategyis in the same package).camel-4x-upgrade-guide-4_21.adoc: does not exist oncamel-4.14.x(modify/delete). Resolved by dropping the 4.21 change and adding a new
=== camel-natssection tocamel-4x-upgrade-guide-4_14.adocon thisbranch. The matching
camel-4x-upgrade-guide-4_14.adocentry onmainis added in a separate doc-sync PR per the backport upgrade-guide policy.
The
camel-natsmodule builds cleanly oncamel-4.14.x(validatedlocally); the full reactor build hits the pre-existing
core/camel-xml-ioschemagen JDK 21 environment issue that also affected #23233 and #23250.
Original description
camel-natsdefaulted itsheaderFilterStrategyto a barenew DefaultHeaderFilterStrategy(), which passes every inbound NATS header(including
Camel*/camel*/org.apache.camel.*) onto the Exchange.This introduces
NatsHeaderFilterStrategy(following theKafkaHeaderFilterStrategy/MailHeaderFilterStrategyshape) and switchesthe default to use it, aligning
camel-natswith the rest of the componentcatalog. Includes a unit test and the upgrade-guide note.
JIRA: https://issues.apache.org/jira/browse/CAMEL-23515 (fixVersions include 4.14.8)
Claude Code on behalf of Andrea Cosentino