ianpriceuk
19-04-08, 20:37
I have got getProductList, getProduct, getCategory and getMerchant working with .NET now and they all work fineon initial inspection, I worked around the dodgy ArrayOfInt problem by editing my Reference.vb/Reference.cs file for the web reference, this will have to be done every AW update, but it saves hassle with the dodgy ShopWondow "ArrayOf" format from the WSDL.
Replace all ArrayOfInt in there with Int64() or equivalent.
However, the searchProduct function appears to be flawed.
I have tried with a populated criteria parameter to it and just an empty freshly initialised one and both just give me an XML error, stating something obscure - "There is an error in XML document (2, 428)." or "There is an error in XML document (2, 345)." if I don't pass the getQuota parameter.
I used Fiddler to ensure the SOAP request was being sent as expected and it is, so the problem must be somewhere in the Web Service itself, and this is quote odd as all others work perfectly.
Anyone got any ideas, had any similar problems, or any of the API developers got any suggestions?
Ian
Replace all ArrayOfInt in there with Int64() or equivalent.
However, the searchProduct function appears to be flawed.
I have tried with a populated criteria parameter to it and just an empty freshly initialised one and both just give me an XML error, stating something obscure - "There is an error in XML document (2, 428)." or "There is an error in XML document (2, 345)." if I don't pass the getQuota parameter.
I used Fiddler to ensure the SOAP request was being sent as expected and it is, so the problem must be somewhere in the Web Service itself, and this is quote odd as all others work perfectly.
Anyone got any ideas, had any similar problems, or any of the API developers got any suggestions?
Ian