VB.NET - Multiple parameters with the same name in a WebMethod

[elTonio]

Hi,

I'm building a VB.Net webMethod that need to receive an already built Soap request, and that request cannot be changed, as it's already in use in our other server, so I'm stuck with it. Actually, the request is made from a PHP script on a Appache server, but the webmethod need to be on an IIS server, using preferably VB.Net.

The exact problem is that the call is built with two parameters, but they have the same names (soapVal). In PHP and Perl (the two language already using this request), they just call the parameters like an array, the names being insignificant.

I tried doing the same using an array having the same name as the parameters in the request, but that did not work. I also tried doing it with a ParamArray, but to no avail.

Is there a way to do this, or am I stuck in doing it in another language/technology?

Thanks in advance

[Plater]

Does it matter what you name the arguments on the VBNet side?
I'm not overly familiar with soap though.

Shouldn't

void SomeFunction(int a, int b)
 

be the same as

void SomeFunction(int atemp, int btemp)
 

[elTonio]

It's what I though, and how I programmed it at first. But when I tested it, I was faced with errors. My parameters are not populated, and the original parameters seem lost.

Here is the body part of the soap envelope I receive:

<SOAP-ENV:Body>
<ns1:getInfo2 xmlns:ns1="http://www.mysite.com/Boutique/Gestion/ws/Commande">
<soapVal xsi:type="xsd:int">2107</soapVal>
<soapVal xsi:type="xsd:string">12345</soapVal>
</ns1:getInfo2>
</SOAP-ENV:Body>

Simply renaming the two parameters soapVal to different names, like soapVal and soapVal2, corrects everything. But it was made clear to me that it is not possible.

Any idea?

[Plater]

Simply renaming the two parameters soapVal to different names, like soapVal and soapVal2, corrects everything. But it was made clear to me that it is not possible.

I take it whoever told you that was either some higher up who knows nothing about this stuff, or the guy who originally did it that way, and doesn't want to have to fix the very obvious mistake he made. Either way it is unfortunate for you.

I am still a bit unclear on some things though.
Like as a soap request you have to build that string yes? And then send it out TO the webservice?
Or do I have this backwards, and you are to be REPLACING the previous webservice and as such, must handle incoming soap requests of that type?

[elTonio]

Or do I have this backwards, and you are to be REPLACING the previous webservice and as such, must handle incoming soap requests of that type?

It's almost that. I'm not replacing an existing service, but replicating the effect of another one. It's for an e-payment application. Here is the structure:

I prepare the order on my site, and when ready I call the Apache server for the payment. I pass to it the transaction number. Then, the Apache server make a Soap call to get the other informations needed for the transaction: amount, taxe, kart content, etc. They pass to me two parameters: the original transaction number I sent them and a siteId. They then proceed with the credit verification (they obtain the credit card number on their own site), show the result to the client and once the transaction is complete they return him to my site.

They are already live, and they have several functioning applications, all in Perl or PHP, who implemented their own werbservices to listen to the payment server call.

My site was bought some months ago, with the IIS servers and technology. I now need (no choice) to use their payment server, and so need to replicate that function, without the possibility of adjusting the soap call.

Is it clearer?

[elTonio]

Finally, I ended up parsing the xml envelope and fetching the values directly in it, with the help of a regex function.