Quantcast
Channel: West Wind Message Board Messages
Viewing all articles
Browse latest Browse all 10393

Naming conflict for Cancel-method

$
0
0
Naming conflict for Cancel-method
Web Service Proxy Generator
Naming conflict for Cancel-method
Jan. 18, 2013
12:15 am
3P100K98EShow this entire thread in new window
Gratar Image based on email address
From:Frits van den Munckhof
To:All
Hi Rick,

The web service I'm comsuming from VFP through your generated proxy contains a method Cancel. When calling this method in the same way as I succesfully called the other methods generated a "Methode Authoriser.Authoriser.Cancel is niet gevonden...". After checking for mistakes in the datatypes I created a breakpoint, to be able to inspect the oService object. oService DID contain "Cancel", but this was a property instead of a method (other methods showing up fine). Do you know where this property is added, since it is not standard attribute of the custom class that you use as your baseclass?

I checked if the Cancel-method was present in the proxy-prg. And it was:

************************************************************************ * Cancel ****************************************FUNCTIONCancel(CardType as String,Requestor as String,TransactionId as Int64) as CancelData

Do you have a workaround to be able to call the Cancel-method of the webservice? Or is this a naming conflict you cancel easily solve in the framework, since Cancel is a pretty obvious method-name for webservices?

TIA, Frits

BTW except for these little startup hickups, everything is working like a dream.

West Wind Web Monitor

Viewing all articles
Browse latest Browse all 10393

Trending Articles