By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,315 Members | 1,672 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,315 IT Pros & Developers. It's quick & easy.

WSDL Generated Proxy Classes Generating Strange SOAP Envelope

P: n/a
I dont think my generated classes are creating a correctly formatted soap
envelope

I have entered the WSDL into the WebServices Studio app (app is from here
http://www.gotdotnet.com/Community/U...4-e916ebc4159c)
and used the Studio to invoke the service.

It gives you the option to view the envelope and it looks like this:-

<?xml version="1.0" encoding="utf-16"?>
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:tns="http://thor.mediaburst.net/wsdl/SearchService"
xmlns:types="http://thor.mediaburst.net/wsdl/SearchService/encodedTypes"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<xsd:string xsi:type="xsd:string">fasdfasd</xsd:string>
</soap:Body>
</soap:Envelope>

There is no function name element and the element which is present should be
called <searchString> not <xsd:string>.

Im sure that this is a problem with the WSDL but it was verifired as ok by
Altova XML Suite. WSDL can be found here
http://www.mediaburst.com/testsite/w...chService.wsdl It imports this wsdl
www.mediaburst.com/testsite/wsdl/Types.wsdl

Thanks for any help.

Ben Crinion
Nov 23 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi,

i tried to take a look at the wdsl's you link to at the bottom of your
post, but i'm getting an access denied.

Can you post them?

Marvin Smit.
On Mon, 24 Oct 2005 14:16:18 +0100, "Ben Crinion"
<be*@dontspam.mediaburst.co.uk> wrote:
I dont think my generated classes are creating a correctly formatted soap
envelope

I have entered the WSDL into the WebServices Studio app (app is from here
http://www.gotdotnet.com/Community/U...4-e916ebc4159c)
and used the Studio to invoke the service.

It gives you the option to view the envelope and it looks like this:-

<?xml version="1.0" encoding="utf-16"?>
<soap:Envelope
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:tns="http://thor.mediaburst.net/wsdl/SearchService"
xmlns:types="http://thor.mediaburst.net/wsdl/SearchService/encodedTypes"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<xsd:string xsi:type="xsd:string">fasdfasd</xsd:string>
</soap:Body>
</soap:Envelope>

There is no function name element and the element which is present should be
called <searchString> not <xsd:string>.

Im sure that this is a problem with the WSDL but it was verifired as ok by
Altova XML Suite. WSDL can be found here
http://www.mediaburst.com/testsite/w...chService.wsdl It imports this wsdl
www.mediaburst.com/testsite/wsdl/Types.wsdl

Thanks for any help.

Ben Crinion

Nov 23 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.