cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Ma <>
Subject null value soap header
Date Wed, 20 Jan 2016 03:10:27 GMT
Hi all,
When I looked at a test case I found SoapOutInterceptor moves nillable
header element to soap body when its value is set to null[1].  For example,
when the following header part value is set to null, this nillable element
will appear in soap body.

public String echo(@WebParam(name = "message") String message.

    @WebParam(name = "paramOut",mode = WebParam.Mode.INOUT, header = true)
Holder<String> paramOut) {
        paramOut.value = null;
        return "echo: " + message;

<soap:Body><ns2:echoResponse xmlns:ns2="urn:echo"><result>echo:
test</result></ns2:echoResponse><ns2:paramOut xmlns:ns2="urn:echo"

Is this nillable element should be still put in soap header ? Is this an
issue or any spec says  this should be handled like this ?



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message