camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-10446) Need to consolidate header mapping logic between Camel and CXF messages
Date Mon, 07 Nov 2016 19:18:59 GMT

     [ https://issues.apache.org/jira/browse/CAMEL-10446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen updated CAMEL-10446:
--------------------------------
    Priority: Minor  (was: Major)

> 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: Improvement
>          Components: camel-cxf, camel-cxfrs
>    Affects Versions: 2.18.0
>            Reporter: Tadayoshi Sato
>            Priority: Minor
>             Fix For: 2.19.0
>
>
> 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)

Mime
View raw message