Problem consuming AXIS service with .Net Framework

[Per Salmi <pe...@syzito.com>]

I have found a problem when using the wsdl.exe from .Net Framework to
generate proxy stub class for a web service that is implemented with Axis.

The web service is published on http://localhost:8080/axis/services/ApplicationService 
but when wsdl.exe generates stub code the port number 8080 is somehow lost
and the wrong URL is in the code, looks like http://localhost/axis/services/ApplicationService.

I have tried generating code stubs for some other web services published on the 
internet where a port number like 8080 is present and from those I got correct and working
stub code with the port number intact. http://213.23.125.181:8080/statistics.wsdl is one of them.

The difference that I can see is that the services with working wsdl documents uses "tns:"
where the Axis generated wsdl uses "intf:".

I don't actually know if it is a problem with .Net tools or Axis but the problem
is not there when using .Net wsdl.exe with other SOAP implementations than Axis.

Has anyone seen this behaviour before? Bug in Axis? Bug in .Net wsdl.exe tool?
 

Re: Problem consuming AXIS service with .Net Framework

[Per Salmi <pe...@syzito.com>]

Maybe I should add that I have tested with Axis Beta 1 and 2002-03-19 build together with RTM version of
.Net Framework and VS.Net RTM version. A few months back I had these things working with VS.Net Beta 2.
But then it was also another Axis build.

/Per Salmi