Handling DOT in Method Name

[Microsoft Newsgroups]

I am trying to consume a web service where there is a dot in the method name
as defined in the portType and binding section of the WSDL file. Here is an
example:

<operation name="soapserve r.login">

The WSDL.EXE tool correctly removes the dot when creating the C# method
name, resulting in soapserverlogin ; however, it also removes the dot when
making the Invoke call as shown:

public loginReturn soapserverlogin (string username, string password) {
object[] results = this.Invoke("so apserverlogin", new object[] {
username,
password});
return ((loginReturn)( results[0]));
}

The web server where the service is located will complain that
"soapserverlogi n" does not exist. If I manually construct the request as
"soapserver.log in", it will work fine.

Does anyone have any advice for handling this issue?

Thanks.

Brian

[Gabriel Lozano-Morán]

Well my primary advice would be to not use dots in operation names. In what
language is this web service implemented by the way that you are allowed to
use dots in the name of the operation?

Gabriel Lozano-Morán

"Microsoft Newsgroups" <br************ @americansentin el.eduwrote in
message news:uO******** ******@TK2MSFTN GP06.phx.gbl...

>I am trying to consume a web service where there is a dot in the method
name as defined in the portType and binding section of the WSDL file. Here
is an example:

<operation name="soapserve r.login">

The WSDL.EXE tool correctly removes the dot when creating the C# method
name, resulting in soapserverlogin ; however, it also removes the dot when
making the Invoke call as shown:

public loginReturn soapserverlogin (string username, string password) {
object[] results = this.Invoke("so apserverlogin", new object[] {
username,
password});
return ((loginReturn)( results[0]));
}

The web server where the service is located will complain that
"soapserverlogi n" does not exist. If I manually construct the request as
"soapserver.log in", it will work fine.

Does anyone have any advice for handling this issue?

Thanks.

Brian

[Brian Carlisle]

It was apparently created using NuSoap in PHP.

I may not be able to get the web service implementation changed. Any advice
on how to handle it?

Brian

"Gabriel Lozano-Morán" <ab***@frontbri dge.comwrote in message
news:e9******** ********@TK2MSF TNGP04.phx.gbl. ..

Well my primary advice would be to not use dots in operation names. In
what language is this web service implemented by the way that you are
allowed to use dots in the name of the operation?

Gabriel Lozano-Morán

"Microsoft Newsgroups" <br************ @americansentin el.eduwrote in
message news:uO******** ******@TK2MSFTN GP06.phx.gbl...

>>I am trying to consume a web service where there is a dot in the method
name as defined in the portType and binding section of the WSDL file.
Here is an example:

<operation name="soapserve r.login">

The WSDL.EXE tool correctly removes the dot when creating the C# method
name, resulting in soapserverlogin ; however, it also removes the dot when
making the Invoke call as shown:

public loginReturn soapserverlogin (string username, string password) {
object[] results = this.Invoke("so apserverlogin", new object[] {
username,
password});
return ((loginReturn)( results[0]));
}

The web server where the service is located will complain that
"soapserverlog in" does not exist. If I manually construct the request as
"soapserver.lo gin", it will work fine.

Does anyone have any advice for handling this issue?

Thanks.

Brian