It was VS.NET (not 2003 beta), but I didn't have Service Pack 1 applied yet, that might fix it.
All in all, it was much easier to get ws interop with Axis than it was with Apache SOAP 2.0. -----Original Message----- From: Steve Loughran [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 27, 2002 7:55 PM To: [EMAIL PROTECTED] Subject: Re: why have to copy .class files of existing webapp into Axis web-inf folder?? ----- Original Message ----- From: "Bates, Alex" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 27, 2002 18:04 Subject: RE: why have to copy .class files of existing webapp into Axis web-inf folder?? > > Good news - it worked! > > I simply copied the servlet declarations from the Axis web.xml into my own > webapp's web.xml (following its own servlet declarations), copied all the > necessary Axis JARs into my lib directory, and voila. > > The axis url becomes > http://myserver:8080/mywebapp/services/myWebService?wsdl > > Also, I created a .NET client for this Axis web service (using .NET's > wsdl.exe), and successfully called a method I'd exposed. > > One note here: the wsdl.exe has a bug in that it missed the :8080 port - so > I had to edit the generated C# file to fix this. I have not encountered that before. What version of .net are you running? Its not the vs.net 2003 beta is it? FYI, ant1.5 has a < wsdltodotnet> wrapper around wsdl.exe, which along with <csc> lets you do interop testing in your build file. -steve
