cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ulhas Bhole <ulhas.bh...@progress.com>
Subject Re: Bug in ReadHeadersInterceptor?
Date Fri, 23 Jan 2009 10:01:28 GMT
I indeed is worng. Please raise a jira and someone will surely take a 
look. (probably me but need to find some time.)

-- Ulhas
Peter Liljenberg wrote:
> 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
>   


Mime
View raw message