[reCoded]

I have the following two web methods in the same web service.

		[WebMethod(MessageName = "Get data by name and part number")]
		[SoapHeader( "WorkEnvironment" )]
		public List<Scratch> GetOpenStatements( string name, string partNumber)
		{

and

		[WebMethod(MessageName = "Get data by last name and part number")]
		[SoapHeader( "WorkEnvironment" )]
		public List<Scratch> GetOpenStatements( string lastName, string partNumber)
		{

I was thinking that is how I could over load the method but for some reason it is not working. Any one have any ideas? Am I overloading these methods correctly?

Thanks,
reCoded

[egof]

It looks like both of your GetOpenStatements have the same signature

1
GetOpenStatements (string,string)
2
GetOpenStatements (string,string)

Here is an example of what your looking for.
http://www.codeproje...L/RefAndOL.aspx

[Diomedes]

I think the issue is that both methods are currently identical from the perspective of the program. They both have the same name, visibility, return type, and arguments. Unless I missed something you just renamed the first string to be "lastName" but it's still a string.

Hence if you think about how you invoke an overloaded method, it looks for a method that would match the name and arguments, but in your case there would be two.

[reCoded]

Thanks. Also it didn't mention that

[WebServiceBinding( ConformsTo = WsiProfiles.None )]

WsiProfiles should be set to None.

[JayFCox]

the following quote has been altered

reCoded, on 16 Jun, 2009 - 10:08 AM, said:

I have the following two web methods in the same web service.

		<snip/>
		public List<Scratch> GetOpenStatements( string name, string partNumber)
		{

and

		<snip/>
		public List<Scratch> GetOpenStatements( string lastName, string partNumber)
		{

<snip/>

Uh????!?!?
Ignore the Web Method anotations.... how is essentially defining the same named function function twice going to work?? Ignore the parameter names, the only way the compiler (or anybody, for that matter) is going to know which one to call is by the parameter TYPES.

[eburger]

reCoded, on 16 Jun, 2009 - 10:08 AM, said:

		[WebMethod(MessageName = "Get data by name and part number")]
		[SoapHeader( "WorkEnvironment" )]
		public List<Scratch> GetOpenStatements( string name, string partNumber)
		{

and

		[WebMethod(MessageName = "Get data by last name and part number")]
		[SoapHeader( "WorkEnvironment" )]
		public List<Scratch> GetOpenStatements( string lastName, string partNumber)
		{

The easiest (and if you haven't made a typing error in your parameters, the only) way to make this work is to simply call your methods GetOpenStatementsByName and GetOpenStatementsByLastName, respectively.

As a side note, you seem to be using the MessageName property as the Description property. The latter is used to describe the web method, the first is to create the externally visible name of the web method (normally, this is the name of the method). This might cause problems, too, as method names cannot contain spaces.

Erik

[baavgai]

eburger, on 17 Jun, 2009 - 01:41 AM, said:

The easiest (and if you haven't made a typing error in your parameters, the only) way to make this work is to simply call your methods GetOpenStatementsByName and GetOpenStatementsByLastName, respectively.

Agree.

Also note that even though you've made methods with identical parameter sigs, it would still fail if you'd done them correctly. Coming into a web service, everything is text. ASP.NET doesn't handle overloading, last time I tried it.

[eburger]

baavgai, on 17 Jun, 2009 - 03:48 AM, said:

Also note that even though you've made methods with identical parameter sigs, it would still fail if you'd done them correctly. Coming into a web service, everything is text. ASP.NET doesn't handle overloading, last time I tried it.

Actually, I believe you can achieve a form of method overloading using the MethodName property of the WebMethod attribute. Assigning a different name to methods with the same name but different parameter signatures will allow you to use method overloading in your web service class without breaking external (i.e. client-side) functionality.

Using identical parameter signatures isn't method overloading, it's method cloning. Method overloading is "the creation of several methods with the same name which differ from each other in terms of the type of the input and the type of the output of the function" [Wikipedia]. There is no programming language that will support method cloning, as the compiler has no idea which of the methods you wish to call.

Just thought I'd clarify

Erik

This post has been edited by eburger: 17 June 2009 - 05:09 AM