Web services are also classes just like any other .NET classes. Nevertheless they have methods marked as WebMethods that can be exposed by the WebServices to be consumed by the outside world. Apart from these WebMethods they can also have normal methods like any other classes have.
Since a web service is a class it can utilize all the OO features like method overloading. However to use this feature on WebMethods we need to do something more that is explained in this article.
Creating WebMethods:
Let us create a simple WebService that has the following overloaded methods:
public int AddNumbers(int a, int b)
public int AddNumbers(int a, int b, int c)
public decimal AddNumbers(decimal a, decimal b)
All these three methods return variants of a Added numbers to the WebClient. Let us now mark the methods as Web Methods. To achieve this apply the [WebMethod] attribute to the public methods.
[WebMethod]
public int AddNumbers(int a, int b) {
return a+b;
}
[WebMethod]
public int AddNumbers(int a, int b, int c) {
return a+b+c;
}
[WebMethod]
public decimal AddNumbers(decimal a, decimal b) {
return a+b;
}
This would compile fine. Run the WebService in the browser. That should give an error saying that the AddNumbers() methods use the same message name 'AddNumbers' and asking to use the MessageName property of the WebMethod.
Adding the MessageName property:
Add the MessageName property to the WebMethod attribute as shown below:
[WebMethod]
public int AddNumbers(int a, int b) {
return "a+b";
}
[WebMethod (MessageName="AddThreeNumbers")]
public int AddNumbers(int a, int b, int c) {
return a + b + c;
}
[WebMethod (MessageName="AddDecimal")]
public decimal AddNumbers(decimal a, decimal b) {
return a+b;
}
Now compile the WebService and run in the browser. You can see that the first method is displayed as AddNumbers wherein for the second and third method the alias we set using the MessageName property is displayed
