Details
-
Improvement
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
2.18.0
-
None
-
Unknown
Description
In the current codebase of camel-cxf and camel-cxf-transport, the header mapping logic between CXF and Camel messages is scattered around DefaultCxfRsBinding, CxfHeaderHelper, and other classes. It should be consolidated into a single place, e.g. CxfHeaderHelper, as much as possible.
I'd like to call it a "bug" because due to this lack of unified header mappings I observe some CXF-specific headers accidentally flow into the Camel world and vice versa.
Attachments
Issue Links
- relates to
-
CAMEL-10429 CXFRS client requires Exchange.HTTP_URI instead of HTTP_PATH for Camel tranport
-
- Resolved
-
- links to