IMPORTANT:
this is not a Support Forum! Experienced users might answer from time to time questions posted here. If you need a professional and reliable answer, or if you want to report a bug, please contact Altova Support instead.

Profile: Mike Murray
About
User Name: Mike Murray
Forum Rank: Newbie
Real Name:
Location Dublin
Occupation:
Interests:
Gender: None Specified
Statistics
Joined: Friday, December 18, 2015
Last Visit: Thursday, January 7, 2016 11:43:46 AM
Number of Posts: 4
[0.02% of all post / 0.00 posts per day]
Avatar
Last 10 Posts
Topic: XMLSpy 2016 Create New Soap Request problem
Posted: Friday, December 18, 2015 10:41:07 AM
island wrote:
Hi,

I would suggest contacting support through the online support form. Provide the exact steps to reproduce the situation as well as access to your webservice.



Thanks Island, our company policy would not allow that, as it is a financial site, but I will contact online support and see if they can help.
In the meantime if anybody on the forums knows how to fix it, I would appreciate the help.
Topic: XMLSpy 2016 Create New Soap Request problem
Posted: Friday, December 18, 2015 10:05:55 AM
I have been using the 2013 and 2015 editions but updated XMLSpy to 2016 recently.
I used XML Spy to test my Soap WCF services because it was a quick and easy process.
But in the new 2016 version of XML Spy the auto generated Soap request for my interface methods are different causing the request to fail.

Here is a soap request generated in the 2015 version which works

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:m0="http://schemas.datacontract.org/2004/07/LeadTrackingInterface">
<SOAP-ENV:Body>
<m:IsGlobalReferralNumber xmlns:m="http://mycompany.com">
<m:request>
<m0:referralNumber>String</m0:referralNumber>
<m0:repCode>String</m0:repCode>
</m:request>
</m:IsGlobalReferralNumber>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Here is the soap request generated in the 2016 version which fails.

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:="http://schemas.datacontract.org/2004/07/LeadTrackingInterface" xmlns:="http://schemas.datacontract.org/2004/07/LeadTrackingInterface">
<SOAP-ENV:Body>
<m:IsGlobalReferralNumber xmlns:m="http://mycompany.com">
<m:request>
<:referralNumber>String</:referralNumber>
<:repCode>String</:repCode>
</m:request>
</m:IsGlobalReferralNumber>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

I see this line is repeated in the XMLSpy 2016 request
xmlns:="http://schemas.datacontract.org/2004/07/LeadTrackingInterface"
and and xmlns:m0= has changed to xmlns:=


Any Ideas why XML Spy is behaving differently for 2016 when generating Soap requests?
Our WCF Service code has not changed in any way.

Below is the error message.






Use of the Altova User Forum(s) is governed by the Altova Terms of Use.