oscerd opened a new pull request, #23321: URL: https://github.com/apache/camel/pull/23321
## 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_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
