Skip to content

[backport camel-4.14.x] CAMEL-23516: camel-xmpp - Use dedicated HeaderFilterStrategy aligned with sibling components#23321

Merged
oscerd merged 1 commit into
apache:camel-4.14.xfrom
oscerd:backport/23283-to-camel-4.14.x
May 19, 2026
Merged

[backport camel-4.14.x] CAMEL-23516: camel-xmpp - Use dedicated HeaderFilterStrategy aligned with sibling components#23321
oscerd merged 1 commit into
apache:camel-4.14.xfrom
oscerd:backport/23283-to-camel-4.14.x

Conversation

@oscerd
Copy link
Copy Markdown
Contributor

@oscerd oscerd commented May 19, 2026

Backport of #23283

Cherry-pick of #23283 onto camel-4.14.x.

Original PR: #23283 - CAMEL-23516: camel-xmpp - Use dedicated HeaderFilterStrategy aligned with sibling components
Original author: @oscerd
Target branch: camel-4.14.x

Conflict resolution

camel-4x-upgrade-guide-4_21.adoc does not exist on camel-4.14.x
(modify/delete). Resolved by dropping the 4.21 change and adding the
equivalent === camel-xmpp note to camel-4x-upgrade-guide-4_14.adoc
on this branch (right after the === camel-nats section from the
CAMEL-23515 backport). The matching camel-4x-upgrade-guide-4_14.adoc
entry on main is added in a separate doc-sync PR per the project's
backport upgrade-guide policy. Code files (XmppEndpoint, XmppBinding,
new XmppHeaderFilterStrategy + test) cherry-picked cleanly.

The camel-xmpp module + new unit test build cleanly on camel-4.14.x
(validated locally); the full reactor build hits the pre-existing
core/camel-xml-io schemagen JDK 21 environment issue that also affected
#23283 / #23296 and the CAMEL-23515 backports.

Original description

camel-xmpp defaulted its headerFilterStrategy to a bare
new DefaultHeaderFilterStrategy() (in XmppEndpoint and the
XmppBinding no-arg constructor), passing inbound XMPP message
properties — including Camel* / camel* / org.apache.camel.*
onto the Exchange. Introduces XmppHeaderFilterStrategy (following the
KafkaHeaderFilterStrategy / MailHeaderFilterStrategy shape) and
switches both defaults to it, aligning camel-xmpp with the rest of the
component catalog. Includes a unit test and the upgrade-guide note.

JIRA: https://issues.apache.org/jira/browse/CAMEL-23516 (fixVersions include 4.14.8)

Claude Code on behalf of Andrea Cosentino

…with sibling components

camel-xmpp defaulted its headerFilterStrategy to a bare
DefaultHeaderFilterStrategy (XmppEndpoint and the XmppBinding no-arg
constructor), passing inbound XMPP message properties — including
Camel* / camel* / org.apache.camel.* — straight onto the Exchange.
Introduces XmppHeaderFilterStrategy (KafkaHeaderFilterStrategy /
MailHeaderFilterStrategy shape) and switches both defaults to it,
aligning camel-xmpp with the rest of the component catalog. Includes a
unit test and the 4.21 upgrade-guide entry. Sibling of CAMEL-23515
(camel-nats). Follow-up to evaluate centralizing this in
DefaultHeaderFilterStrategy is tracked as CAMEL-23543.

Closes apache#23283

(cherry picked from commit 4a07498)
@oscerd oscerd merged commit e334228 into apache:camel-4.14.x May 19, 2026
3 checks passed
@oscerd oscerd deleted the backport/23283-to-camel-4.14.x branch May 19, 2026 09:47
oscerd added a commit that referenced this pull request May 19, 2026
The camel-xmpp HeaderFilterStrategy change was backported to camel-4.14.x
(#23321, merged). Per the project's backport upgrade-guide policy, the
version-specific camel-4x-upgrade-guide-4_14.adoc lives canonically on main
across all releases. This adds the matching === camel-xmpp section to that
guide on main so the canonical history does not drift from the maintenance
branch.

Docs-only; no code or build impact.

Closes #23325
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants