Inside the WSDL & Web Services Proxies
page 11 of 16
by Anonymous Contributor
Feedback
Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 65491/ 115

Web Service Client Rules for Inheritors: Rule #1

Any Web Service client using ASP.NET needs to declare a class deriving indirectly from WebClientProtocol. I used the word “indirectly” because, there are sub classes under WebClientProtocol that are specific to the protocol that we decided to use while communicating the Web Service. They are

? ? SoapHttpClientProtocol for SOAP

? ? HttpGetClientProtocol for HTTP-GET

? ? HttpPostClientProtocol for HTPP-POST

All the three classes mentioned above are derived directly or indirectly from WebClientProtocol class. 

For example:

public class SoapCall : System.Web.Services.Protocols.SoapHttpClientProtocol


View Entire Article

User Comments

Title: Webservice   
Name: Anbazhagan. P
Date: 2009-03-14 12:47:38 PM
Comment:
Very useful website
Title: rakesh   
Name: Name rakesh
Date: 2007-09-13 3:38:58 AM
Comment:
Ok Run
Title: Getting Error   
Name: Dilip Kumar Prusty
Date: 2006-09-18 5:19:48 AM
Comment:
I am getting
The request failed with HTTP status 404: Not Found.
this error .

Product Spotlight
Product Spotlight 





Community Advice: ASP | SQL | XML | Regular Expressions | Windows


©Copyright 1998-2024 ASPAlliance.com  |  Page Processed at 2024-03-28 7:01:01 AM  AspAlliance Recent Articles RSS Feed
About ASPAlliance | Newsgroups | Advertise | Authors | Email Lists | Feedback | Link To Us | Privacy | Search