[
https://issues.apache.org/jira/browse/CAMEL-23759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18089226#comment-18089226
]
Andrea Cosentino commented on CAMEL-23759:
------------------------------------------
Main fix merged to 4.21.0 (squash c5b27e035e, PR #24030). Upgrade-guide
doc-sync of the camel-spring-ws entry to the 4.18 and 4.14 guides on main: PR
#24035. Code backports to camel-4.18.x (4.18.3) and camel-4.14.x (4.14.8) still
pending.
_Claude Code on behalf of Andrea Cosentino_
> camel-spring-ws: apply a HeaderFilterStrategy to inbound SOAP headers
> ---------------------------------------------------------------------
>
> Key: CAMEL-23759
> URL: https://issues.apache.org/jira/browse/CAMEL-23759
> Project: Camel
> Issue Type: Improvement
> Components: camel-spring-ws
> Reporter: Andrea Cosentino
> Assignee: Andrea Cosentino
> Priority: Major
> Fix For: 4.14.8, 4.18.3, 4.21.0
>
>
> The spring-ws consumer maps the names of inbound SOAP header elements and
> attributes directly into the Camel Exchange header map. Other Camel
> components apply a HeaderFilterStrategy on the inbound path so that the
> internal Camel / camel / org.apache.camel.* header namespace is managed by
> Camel rather than taken verbatim from external input.
> This adds a configurable headerFilterStrategy endpoint option to
> camel-spring-ws, defaulting to a new SpringWebserviceHeaderFilterStrategy
> that filters the Camel*/camel* namespace (case-insensitive) in both inbound
> and outbound directions, for consistency with components such as camel-cxf,
> camel-mail and camel-coap.
> Potential breaking change: inbound SOAP header element/attribute names in the
> Camel*/org.apache.camel.* namespace are no longer propagated as Exchange
> headers. A custom headerFilterStrategy can be supplied to restore the
> previous behaviour. Documented in the 4.21 upgrade guide.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
