I could reproduce that error on my redhat9 box. And when I adjusted System.Xml.XmlStreamReader not to use XmlInputStream, wsdl.exe successfully generates bloggyWS.cs.
However, when I tried that URL with mono's wsdl.exe both on mono runtime and on MS .NET runtime (without that xml change), it generated bloggyWS.cs successfully.
So there looks a bug somewhere in network stream and/or XmlInputStream, which is specific to linux or unix environment. (However, there is no code switch in XmlInputStream.)
Anyways, please file a bug as far as you know.
Thanks, Atsushi Eno
Pablo Fischer wrote:
Ohh..
So, should I report it as a bug? a 'network stream bug'?
Happy new year! Pablo El dom, 28-12-2003 a las 17:29, David Sheldon escribi�:
On Sun, Dec 28, 2003 at 12:39:11PM -0600, Pablo Fischer wrote:
Hi!
Yep, I know that in .NET Framework I can generate the proxy code, but I'm not using Windows, I'm using Mono in Linux, and in Mono the wsdl.exe can't generate the proxy code.
If you save the wsdl to a file, then run wsdl on that file it appears to generate correct code. Unfortunately I don't have time to work on this at the moment, but it does look like a bug in reading XML from a network stream.
Coincidently, the close-tag that is failing is the same one that the IP
packet spilts, but I can't see how that would break it.
David
_______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
