We tried to use soapheaders by adding a HeaderProcessor. When looking at the
CXF code (2.1.2) we find this:
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);
}
This might be fixed in later version already, or there might even exist an
issue for this?
/Peter
--
View this message in context:
http://www.nabble.com/Bug-in-ReadHeadersInterceptor--tp21621240p21621240.html
Sent from the cxf-dev mailing list archive at Nabble.com.
