This is an automated email from the ASF dual-hosted git repository.

oscerd pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new cdc653298383 CAMEL-23516: docs - sync camel-xmpp 4.14 upgrade-guide 
entry to main
cdc653298383 is described below

commit cdc6532983835792c6fab774a56fc47969c8c7bd
Author: Andrea Cosentino <[email protected]>
AuthorDate: Tue May 19 12:02:26 2026 +0200

    CAMEL-23516: docs - sync camel-xmpp 4.14 upgrade-guide entry to main
    
    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
---
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc          | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
index 3cb824f779ff..ec0784b06b8d 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
@@ -264,3 +264,12 @@ aligning the component with the rest of the Camel 
component catalog (`camel-kafk
 `camel-coap`, `camel-google-pubsub`, ...). Routes that relied on passing 
through these header
 names from NATS messages can supply a custom `headerFilterStrategy` to restore 
the previous
 behaviour.
+
+=== camel-xmpp
+
+The default `headerFilterStrategy` is now a new `XmppHeaderFilterStrategy` 
that filters headers
+starting with `Camel` / `camel` (case-insensitive) in both the inbound and 
outbound directions,
+aligning the component with the rest of the Camel component catalog 
(`camel-kafka`, `camel-mail`,
+`camel-coap`, `camel-google-pubsub`, ...). Routes that relied on passing 
through these header
+names from XMPP messages can supply a custom `headerFilterStrategy` to restore 
the previous
+behaviour.

Reply via email to