[CXF-6751] Nillable header element is missing in soap header

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.0.7, 3.1.4
• Component/s: Soap Binding
• Estimated Complexity: Unknown
• Assignee: Jim Ma
• Reporter: Jim Ma
• Created: 21/Jan/16 06:23
• Updated: 04/May/17 19:51

Description

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.
<code>
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; }

</code>
<soap:Body><ns2:echoResponse xmlns:ns2="urn:echo"><result>echo: test</result></ns2:echoResponse><ns2:paramOut xmlns:ns2="urn:echo" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/></soap:Body>

Issue Links

• duplicates: CXF-6752 Nillable header element is missing in soap header