Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Namespace prefix is required on first element when elementFormDefault=unqualified #905

Merged
merged 1 commit into from
Dec 14, 2016

Conversation

aleung
Copy link
Contributor

@aleung aleung commented Dec 14, 2016

This PR fixes an issue that the namespace prefix was missing on the first element in SOAP body.

In below example, this PR adds the tns in <tns:execFileParams>.

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:tns="urn:FileExecutor">
  <soap:Body>
    <tns:execFileParams>
      <fileName>PSTN</fileName>
      <arguments>abc</arguments>
      <base64EncodedStdIn>dGVzdA==</base64EncodedStdIn>
      <startDetached>true</startDetached>
    </tns:execFileParams>
  </soap:Body>
</soap:Envelope>

I have crosschecked the generated SOAP request in SoapUI-5.2.1 using the same WSDL.

@coveralls
Copy link

coveralls commented Dec 14, 2016

Coverage Status

Coverage increased (+0.007%) to 93.144% when pulling 019a921 on aleung:missing_ns_prefix into 0544cc7 on vpulim:master.

@jsdevel jsdevel merged commit 2ca1858 into vpulim:master Dec 14, 2016
@aleung aleung deleted the missing_ns_prefix branch December 15, 2016 06:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants