oscerd opened a new pull request, #23376:
URL: https://github.com/apache/camel/pull/23376
## Backport of #23326
Cherry-pick of #23326 onto `camel-4.14.x`.
- **Original PR:** apache/camel#23326 — *CAMEL-23526: camel-cxf - align
Exchange header constant names with Camel naming convention*
- **4.18.x backport:** apache/camel#23369 (merged)
- **Original author:** @oscerd
- **Target branch:** `camel-4.14.x`
- **Squash merge cherry-picked:** `7240570a056`
### Manual adjustments during cherry-pick
- **Upgrade-guide entry moved** from `camel-4x-upgrade-guide-4_21.adoc`
(does not
exist on this branch) to `camel-4x-upgrade-guide-4_14.adoc`, appended
after the
existing `=== camel-aws2-sqs` / `=== camel-aws2-sns` entries that recently
landed on this branch via CAMEL-23506. The matching `4_14.adoc` entry on
`main`
will be synced in a follow-up PR per CLAUDE.md's backport upgrade-guide
policy.
- **Resolved import conflict** in `CxfPayloadProviderRouterTest.java`: kept
only the `CxfConstants` import; left the existing FQCN usage of
`org.apache.cxf.endpoint.Client` / `ClientProxy` intact to avoid pulling in
the unrelated OpenRewrite FQCN refactor that only exists on `main`.
- **Regenerated** component metadata, catalog, and endpoint DSL using
4.14.x's generators (full reactor build, `-DskipTests`).
### Behaviour change carried over
Because the renamed header value now begins with `Camel`, it is filtered by
transport `HeaderFilterStrategy` (`JmsHeaderFilterStrategy`,
`HttpHeaderFilterStrategy`, etc.) at every transport boundary. Routes that
bridge an external transport into a `cxf:` producer must carry the operation
in a non-`Camel`-prefixed application header and map it to
`CxfConstants.OPERATION_NAME` between the transport `from` and the `cxf:`
`to`.
The 4.14 upgrade guide entry documents this with the standard before/after
example.
JIRA: https://issues.apache.org/jira/browse/CAMEL-23526
---
_Backport prepared by 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]
