Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-10446

Need to consolidate header mapping logic between Camel and CXF messages

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 2.18.0
    • 2.19.0
    • camel-cxf, camel-cxfrs
    • 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

          Bug - A problem which impairs or prevents the functions of the product. CAMEL-10429 CXFRS client requires Exchange.HTTP_URI instead of HTTP_PATH for Camel tranport

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          links to

          Web Link GitHub Pull Request #1253

          Activity

            People

              davsclaus Claus Ibsen
              tadayosi Tadayoshi Sato
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: