You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Tadayoshi Sato (JIRA)" <ji...@apache.org> on 2016/11/05 12:33:58 UTC
[jira] [Created] (CAMEL-10446) Need to consolidate header mapping
logic between Camel and CXF messages
Tadayoshi Sato created CAMEL-10446:
--------------------------------------
Summary: Need to consolidate header mapping logic between Camel and CXF messages
Key: CAMEL-10446
URL: https://issues.apache.org/jira/browse/CAMEL-10446
Project: Camel
Issue Type: Bug
Components: camel-cxf, camel-cxfrs
Affects Versions: 2.18.0
Reporter: Tadayoshi Sato
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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)