This is using eBay's Large Merchant Services, although I'm sure it's similar tot he Merchat API where the schema comes from.
I was getting an error for a long time that said something to the effect of "Invalid Data". Very descriptive by the way.
It turns out I was getting this error because only certain values are accepted in the <ShippingService> tag. Does anyone know what these values are? If I enter <ShippingService>USPSPriority</ShippingService> everythign works fine. What if I am shipping UPS? Ground, 2nd Day Air, etc? What are the valid values so that the service doesn't just throw up at me with "invalid data"? Also, why is this not in the schema? If it says string then it should allow any string. If you want specific values then they should be identified.
I've also noticed that LMS requires alot of fields, even though the schema does not. I get a failed addfixeditem because I'm missing one thing or another. Isn't this supposed to the point of a schema in the first place? If I have a payload that validates against your schema you should accept it and process it, not reject it and say "I also want X". When it takes 2-5 minutes to send a payload to the sandbox just to find out you are missing something else AGAIN it gets very frustrating.
Posts:
37
Member Since:
6/10/09
Re: What are valid values for ShippingService?
Posted:
Nov 19, 2009 9:41 AM
Yes, I noticed that after the fact. JAXB translates that into a String upon marshalling, that must be where I got it from, although Token is derived from string and basically just means that it "will remove line feeds, carriage returns, tabs, leading and trailing spaces, and multiple spaces." (http://www.w3schools.com/Schema/schema_dtypes_string.asp)
Posts:
18
Member Since:
11/16/09
Re: What are valid values for ShippingService?
Posted:
Nov 19, 2009 10:55 AM
