oscerd opened a new pull request, #27211:
URL: https://github.com/apache/camel/pull/27211

   ## Description
   
   [CAMEL-25225](https://issues.apache.org/jira/browse/CAMEL-25225)
   
   CAMEL-23759 added the `headerFilterStrategy` option to camel-spring-ws and 
applied it in `SpringWebserviceConsumer`, where inbound SOAP header attributes 
and elements are mapped to Exchange headers. The producer did not consult it. 
With `allowResponseHeaderOverride=true`, 
`SpringWebserviceProducer.populateMessageHeaderFromResponse` copied every SOAP 
response header attribute and element into the message headers by local name, 
including names in the `Camel*` namespace.
   
   ## Changes
   
   - `SpringWebserviceProducer`: applies the endpoint's `headerFilterStrategy` 
(`applyFilterToExternalHeaders`) to both the attribute loop and the element 
loop of the response mapping, the same way the consumer does. The raw SOAP 
header (`CamelSpringWebserviceSoapHeader`) is still set.
   - The `allowResponseHeaderOverride` option description now mentions the 
filtering. The component JSON, catalog and endpoint DSL are regenerated.
   - New `ProducerSoapHeaderFilterTest` covering:
     - attribute, element and case-variant `Camel*` names are filtered;
     - application-level attributes and elements are still mapped;
     - a custom pass-through `headerFilterStrategy` configured on the endpoint 
is honoured.
   - Upgrade guide notes in 4_23, in 4_22 (4.22.1 to 4.22.2) and in 4_18 
(4.18.4 to 4.18.5). The change is meant to be backported to `camel-4.22.x` and 
`camel-4.18.x` once merged.
   
   ## Testing
   
   - `mvn clean install` in `components/camel-spring-parent/camel-spring-ws`: 
96 tests, 0 failures.
   - The new filter tests fail against the previous producer code and pass with 
this change.
   - Full reactor build from the root: `mvn clean install -DskipTests`.
   
   _Claude Code on behalf of oscerd_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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]

Reply via email to