Have you seen Simon Fell's utilities (tcpTrace, proxyTrace, and YATT) at PocketSoap.com? By looking at the actual message, this helps debugging tremendously.
Kirk Allen Evans Author, "XML And ASP.NET", New Riders Publishing www.xmlandasp.net Read my web log at http://weblogs.asp.net/kaevans > -----Original Message----- > From: Moderated discussion of advanced .NET topics. [mailto:ADVANCED- > [EMAIL PROTECTED] On Behalf Of Curtis Koppang > Sent: Friday, June 06, 2003 2:44 PM > To: [EMAIL PROTECTED] > > I am currently getting an exception in a proxy I generated. This is the > third issue I have stumbled upon; each of the previous issues was because > of "invalid" WSDL or schema. Which leads me to a bigger question... > > Is it just me or does this architecture seem way to hard to debug? > > It seems like so much of the implementation is hidden from me its > impossible for me to figure what I did wrong. So how do you debug this > stuff? Is there a better (more low level) way to do this where I have to > do a little more work, but I see more of the actual code? Are there any > rigorous WSDL validators out there? I used the one built into XML Spy and > it gives me the thumbs up on my WSDL/Schema. > > Any insight would be greatly appreciated, > curt
