You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cxf.apache.org by "Venkat (JIRA)" <ji...@apache.org> on 2015/05/21 19:33:17 UTC

[jira] [Updated] (CXF-6418) JavaScript client incorrect serialization when SoapHeader is defined

     [ https://issues.apache.org/jira/browse/CXF-6418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Venkat updated CXF-6418:
------------------------
    Summary: JavaScript client incorrect serialization when SoapHeader is defined  (was: JavaScript client incorrect serialization when SopaHeader are defined)

> JavaScript client incorrect serialization when SoapHeader is defined
> --------------------------------------------------------------------
>
>                 Key: CXF-6418
>                 URL: https://issues.apache.org/jira/browse/CXF-6418
>             Project: CXF
>          Issue Type: Bug
>          Components: JavaScript Client
>    Affects Versions: 3.0.4
>         Environment: Windows 7, AIX, Linux
>            Reporter: Venkat
>         Attachments: ApplException.xsd, TestServiceSoapHeader.js, incorrectsoapmessage.xml, someType.xsd, test.wsdl, test.xsd
>
>
> wsdl2js generates the client code when request soap header present. But the request serialization does not include <soap:header>...</soap:header> block at all. Both header part and message part are included in the <soap:body>.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)