Well, that is not doable in my scenerio. I have Windows Service running and generating Google Base feeds for our clients.
If Windows Service encounters and error it reports to me that something failed ( in this case it reports "Bad Request" as the reason for the failure). If its very critical, instead of building XML feed and testing with the the page you mentioned above, I use Network sniffer (i find this approach much faster). Never the less, I believe this is a small but very inconvinient bug in Client APIs, "Errors" property should see all the errors, or I should have ability to read full response and find errors myself. Is there way Google Team can fix this? On Oct 8, 5:21 pm, Alex <[email protected]> wrote: > No, don't stop using the client library. > I am suggesting that for debug purposes you should try to use the demo page, > if you have the input XML. Then, you can see what you > get back from the server directly, including the errors. Then hopefully > you can understand what went wrong, fix the code/data and resubmit. > > Alex > > > > > > On Thu, Oct 8, 2009 at 11:17 PM, igs <[email protected]> wrote: > > > Alex, > > thank your reply. > > > The page you were reffering seems to be using XML Webserive. > > > I'm using Clinet API for .NET, and it hides XML Request and XML > > Response from the developer. > > > Are you suggesting to abandon Client APIs, and try to communicate > > straight with Google Webserive? > > (that makes Client APIs sort of useless) > > > On Oct 8, 3:51 pm, Alex <[email protected]> wrote: > > > You can use the Base API demo page to execute batch requests, and then > > you > > > can also see what is the response. > > > I suggest you find a way to build the request as in production (XML), and > > go > > > here and execute the request (select batch, and fill in your batch > > request):http://www.google.com/base/api/demo/html/demo.html > > > > Then you'll see the errors. I can't comment on how to code it, because I > > > don't know what client library you use. > > > > Alex > > > > On Thu, Oct 8, 2009 at 9:32 PM, igs <[email protected]> wrote: > > > > > Anybody?? > > > > > Anybody from Google Support Team? > > > > > I need the resolution for this. > > > > > On Oct 6, 2:57 pm, igs <[email protected]> wrote: > > > > > After batch of items is submitted through API, I check the status of > > > > > each item to see if it was successful by checking: > > > > > entry.BatchData.Status.Code > > > > > > if Code is greater 300 (error), "entry.BatchData.Status.Reason" > > > > > returns static useless message "Bad request". > > > > > > In my testing environment the only way I would see actual error, is > > by > > > > > using Network Sniffer and look at HTTP responses from Google Server. > > > > > > It's not possible for me to sniff traffic In production environment, > > > > > and it leaves me guessing what might be the problem. > > > > > > I saw that there is a property "Errors" in "entry.BatchData.Status" > > > > > which is always empty. > > > > > > Is this a bug, and "Errors" should actually carry detailed errors, or > > > > > am I doing something wrong? > > > > > > How do I find exact error without using network sniffer? > > > > -- > > > Alex Dovlecel, Google Switzerland GmbH > > > Company Identifikationsnummer: CH-020.4.028.116-1- Hide quoted text - > > > > - Show quoted text - > > -- > Alex Dovlecel, Google Switzerland GmbH > Company Identifikationsnummer: CH-020.4.028.116-1- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Base Data API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-base-data-api?hl=en -~----------~----~----~----~------~----~------~--~---
