ReadHeadersInterceptor ignoring DataBinding when creating SoapHeader
--------------------------------------------------------------------
Key: CXF-2000
URL: https://issues.apache.org/jira/browse/CXF-2000
Project: CXF
Issue Type: Bug
Components: Soap Binding
Affects Versions: 2.1.2
Reporter: Peter Liljenberg
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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
