I am writing an Axis client to interface with a VB.NET soap service and
I am having an issue with the axis client (vb client apparently works)
where the soap service is not getting the string being passed through
the only function and argument the service takes. Below are the two
envelopes. What could be causing this? Since it is authenticating, I am
pretty sure the problem is in the body of the envelope and not the
header. I am at a loss since the differences (see testpostdata and
xmldata elements) between these two are minimal and seem to be more
semantic than anything of substance.
Thanks in advance,
Tom
VB.Net Client envelope
<?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:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Header>
<cAuthentication xmlns="http://ar.masstech-pts.org/">
<UserName>username</UserName>
<Password>******</Password>
</cAuthentication>
</soap:Header>
<soap:Body>
<testpostdata xmlns="http://ar.masstech-pts.org/">
<xmldata>String Here...
</xmldata>
</testpostdata></soap:Body></soap:Envelope>
Axis client envelope
<?xml version="1.0" encoding="UTF-8"?>
<soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Header>
<ns1:cAuthentication soapenv:mustUnderstand="0"
xmlns:ns1="http://ar.masstech-pts.org/">
<ns1:UserName>username</ns1:UserName>
<ns1:Password>*******</ns1:Password>
</ns1:cAuthentication>
</soapenv:Header>
<soapenv:Body>
<testpostdata
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<xmldata xsi:type="xsd:string">String Here...
</xmldata>
</testpostdata>
</soapenv:Body>
- Re: .NET compat issue... Thomas Bolioli
- Re: .NET compat issue... Dan Christopherson
- Re: .NET compat issue... Thomas Bolioli
- Re: .NET compat issue... Jim Murphy
- Re: .NET compat issue... Dennis Sosnoski
- Re: .NET compat issue... Thomas Bolioli
- Re: .NET compat issue... Dennis Sosnoski
- Re: .NET compat issue... Thomas Bolioli
