View Single Post
  #2 (permalink)  
Old February 25th, 2004, 08:30 AM
planoie's Avatar
planoie planoie is offline
Friend of Wrox
Points: 16,481, Level: 55
Points: 16,481, Level: 55 Points: 16,481, Level: 55 Points: 16,481, Level: 55
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Aug 2003
Location: Clifton Park, New York, USA.
Posts: 5,407
Thanks: 0
Thanked 16 Times in 16 Posts
Default

A .NET web service is nothing more than XML. Even if the web service only supports SOAP requests, you could still consume the web service without using a SOAP helper. You could manually construct a SOAP request that gets posted to the web service. If the web service supports standard POST or GET then the news is even better. The best is if it supports GET because you simply need to call the web service with a standard GET call.

The MS XML 4.0 object you would use in a VB6 application supports such calls. You just ask it to open XML from a URL. You can construct the web service URL with all the necessary arguments on the query string. Then it's just a matter of knowing the XML structure returned so you know what to query with xpath. The SOAP stuff of the returned XML can be ignored.

Peter
------------------------------------------------------
Work smarter, not harder.
Reply With Quote