Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-2000

ReadHeadersInterceptor ignoring DataBinding when creating SoapHeader

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.2
    • Fix Version/s: 2.0.10, 2.1.4
    • Component/s: Soap Binding
    • Labels:
      None

      Description

      We tried to use soapheaders by adding a HeaderProcessor. When looking at the CXF code (2.1.2) we find this in ReadHeadersInterceptor:

      HeaderProcessor p = bus.getExtension(HeaderManager.class)
      .getHeaderProcessor(hel.getNamespaceURI());

      Object obj;
      DataBinding dataBinding = null;
      if (p == null || p.getDataBinding() == null) {
      obj = node;
      } else

      { obj = p.getDataBinding().createReader(Node.class).read(node); } //TODO - add the interceptors SoapHeader shead = new SoapHeader(new QName(node.getNamespaceURI(),node.getLocalName()), obj, dataBinding); This looks like a bug to me. Should the dataBinding that is extraced be used when constructing the SoapHeader instead of ALWAYS be null. I'm just guessing but shouldn't it look like this: }

      else {
      dataBinding = p.getDataBinding();
      obj = dataBinding.createReader(Node.class).read(node);

      http://www.nabble.com/Bug-in-ReadHeadersInterceptor--td21621240.html

        Attachments

          Activity

            People

            • Assignee:
              dkulp Daniel Kulp
              Reporter:
              pliljenberg@gmail.com Peter Liljenberg
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: