Welcome! and rules
Joel on Software
Calling web services from old-style ASPages
So I've finally found a problem that actually requires a solution that needs all this new-fangled web services shenanigans (sharing HTML headers and footers across many webservers) and I'm stumped on this one: how do the old apps access the brand new web service that spoons out the HTML. I'm particularly interested in ASP (most of our apps) but also Cold Fusion and Java. A quick scout around the web gave me nothing much of any use. Its easy to change their "GetHeader" shared lib to do the right thing I'm just not sure what the "right thing" is - do I need to install some kind of SOAP-enabling components on each webserver?
That's perfect thanks. Why the wdsl on the end of the URL?
The WSDL file is an XML file that describes all the methods and their parameters in a web service. When you create the soapClient it uses the WSDL file to know what method to call. Adding '?wsdl' to the end of a url to a .NET service is how you get the XML description of the service.
When you create a WebService project in .NET and run it from the debugger, it launches a web page that has examples for calling your service using SOAP, HTTP GET, and HTTP POST. It also creates a test harness for your service. This is a nifty little feature of .NET that I really like.
Fog Creek Home