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 6a64636314f1 CAMEL-23759: camel-spring-ws - sync upgrade-guide entry 
to 4.18/4.14 guides on main
6a64636314f1 is described below

commit 6a64636314f1f3dbd77732ae92ad4cbc148c9ee5
Author: Andrea Cosentino <[email protected]>
AuthorDate: Tue Jun 16 09:16:53 2026 +0200

    CAMEL-23759: camel-spring-ws - sync upgrade-guide entry to 4.18/4.14 guides 
on main
    
    Adds the camel-spring-ws header-filtering upgrade-guide entry (merged for 
4.21.0 in #24030) to the canonical version-specific guides on main: 
camel-4x-upgrade-guide-4_18.adoc (4.18.3) and camel-4x-upgrade-guide-4_14.adoc 
(4.14.8), per the backport upgrade-guide policy, since the fix is fixVersioned 
for those maintenance lines.
    
    Closes #24035
---
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc       | 11 +++++++++++
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc       | 11 +++++++++++
 2 files changed, 22 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 5fe9b32ad287..83f4d359ebb4 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
@@ -13,6 +13,17 @@ See the xref:camel-upgrade-recipes-tool.adoc[documentation] 
page for details.
 
 == Upgrading from 4.14.3 to 4.14.8
 
+=== camel-spring-ws - potential breaking change
+
+The `spring-ws` consumer now applies a `HeaderFilterStrategy` to the SOAP 
headers it maps onto the
+Camel `Exchange`. The default `headerFilterStrategy` is a new 
`SpringWebserviceHeaderFilterStrategy`
+that filters header names 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-cxf`, `camel-mail`, `camel-coap`, ...). SOAP header element and 
attribute names that fall in
+that namespace are no longer propagated as `Exchange` headers. Routes that 
relied on receiving such
+header names from inbound SOAP headers can supply a custom 
`headerFilterStrategy` (via the new
+`headerFilterStrategy` endpoint option) to restore the previous behaviour.
+
 === camel-netty-http / camel-undertow - potential breaking change
 
 The `muteException` consumer option now defaults to `true` in 
`camel-netty-http` and
diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
index 4469e95d457c..c5635c624f42 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
@@ -13,6 +13,17 @@ See the xref:camel-upgrade-recipes-tool.adoc[documentation] 
page for details.
 
 == Upgrading from 4.18.1 to 4.18.3
 
+=== camel-spring-ws - potential breaking change
+
+The `spring-ws` consumer now applies a `HeaderFilterStrategy` to the SOAP 
headers it maps onto the
+Camel `Exchange`. The default `headerFilterStrategy` is a new 
`SpringWebserviceHeaderFilterStrategy`
+that filters header names 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-cxf`, `camel-mail`, `camel-coap`, ...). SOAP header element and 
attribute names that fall in
+that namespace are no longer propagated as `Exchange` headers. Routes that 
relied on receiving such
+header names from inbound SOAP headers can supply a custom 
`headerFilterStrategy` (via the new
+`headerFilterStrategy` endpoint option) to restore the previous behaviour.
+
 === camel-netty-http / camel-undertow - potential breaking change
 
 The `muteException` consumer option now defaults to `true` in 
`camel-netty-http` and

Reply via email to