> I tried that and got the errors as shown below.
Oops, forgot the errors did I?! :)
Here they are:
C:\Temp>wsdl /out:myproxyclass.cs
http://srv019v:9000/test/iWayCallout.ibs?wsdl
Microsoft (R) Web Services Description Language Utility
[Microsoft (R) .NET Framework, Version 2.0.50727.42]
Copyright (C) Microsoft Corporation. All rights reserved.
Error: There was an error processing
'http://srv019v:9000/test/iWayCallout.ibs?wsdl'.
- The document at the url http://srv019v:9000/test/iWayCallout.ibs?wsdl
was not recognized as a known document type.
The error message from each known type may help you fix the problem:
- Report from 'DISCO Document' is 'Discovery document at the URL
http://srv019v:9000/test/iWayCallout.ibs?wsdl could not be found.'.
- The document format is not recognized.
- Report from 'WSDL Document' is 'There is an error in XML document (1,
3357).'.
- The element was not expected in this context: <xs:simpleType
xmlns:xs='http://www.w3.org/2001/XMLSchema'>..</xs:simpleType>. Expected el
ements: http://www.w3.org/2001/XMLSchema:annotation,
http://www.w3.org/2001/XMLSchema:element,
http://www.w3.org/2001/XMLSchema:sequence, ht
tp://www.w3.org/2001/XMLSchema:any, http://www.w3.org/2001/XMLSchema:choice,
http://www.w3.org/2001/XMLSchema:group.
- Report from 'XML Schema' is 'The root element of a W3C XML Schema should
be <schema> and its namespace should be 'http://www.w3.org/2001/X
MLSchema'.'.
If you would like more help, please type "wsdl /?".
>> I tried that and got the errors as shown below.
>
> Which errors?
Marc Gravell - 19 Mar 2008 07:49 GMT
It begs the question of whether their wsdl is well formed. I don't
know enough about wsdl to answer off the top of my head... but from
the error it certainly isn't what wsdl.exe is expecting. Hard to tell
without visibility of the wsdl, unfortunately...
Marc