You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Dennis Kieselhorst (JIRA)" <ji...@apache.org> on 2017/05/15 19:19:04 UTC
[jira] [Resolved] (CXF-6752) Nillable header element is missing in
soap header
[ https://issues.apache.org/jira/browse/CXF-6752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Kieselhorst resolved CXF-6752.
-------------------------------------
Resolution: Duplicate
> Nillable header element is missing in soap header
> -------------------------------------------------
>
> Key: CXF-6752
> URL: https://issues.apache.org/jira/browse/CXF-6752
> Project: CXF
> Issue Type: Bug
> Components: Soap Binding
> Affects Versions: 3.0.7, 3.1.4
> Reporter: Jim Ma
> Assignee: Jim Ma
>
> 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>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)