A
Andy Fish
Hi,
I have discovered that if I use this syntax:
[WebMethod(MessageName="foo")]
public string bar() {
return "hello, world";
}
then it is not possible to call the web service using the MS soap toolkit.
Trying to invoke the service with either the name foo or bar gives an error.
I'm afraid I'm not much of an expert on SOAP and WSDL (I was rather hoping
that using 2 microsoft implementations of the same standard would give me a
good chance of interoperability without having to delve into the innards of
the standard)
Could someone explain whether this is a deficiency in the SOAP toolkit, or
is this feature (the ability to have the operation name different from the
SOAP action) an unofficial .Net extension of the web services standards?
TIA
Andy
I have discovered that if I use this syntax:
[WebMethod(MessageName="foo")]
public string bar() {
return "hello, world";
}
then it is not possible to call the web service using the MS soap toolkit.
Trying to invoke the service with either the name foo or bar gives an error.
I'm afraid I'm not much of an expert on SOAP and WSDL (I was rather hoping
that using 2 microsoft implementations of the same standard would give me a
good chance of interoperability without having to delve into the innards of
the standard)
Could someone explain whether this is a deficiency in the SOAP toolkit, or
is this feature (the ability to have the operation name different from the
SOAP action) an unofficial .Net extension of the web services standards?
TIA
Andy