Thanks Aron. Your request sounds very reasonable, and I will pass it on to the appropriate people.
Cheers, -Ryan On Apr 6, 12:26 pm, "Aron" <[EMAIL PROTECTED]> wrote: > The following thread is pertinent in a Google Calendar Data API > context, as well as likely in other GData API contexts: > > http://groups.google.com/group/google-help-dataapi/browse_thread/thre... > > To summarize that thread: many Exceptions returned from the Calendar > Data API, as well as those returned generally from the GData API, are > returned as instance of ServiceException and its subclasses. > > However, those Exceptions' getMessage() methods often return only > generic and thus unhelpful messages. The 'real,' underlying, and > helpful error or status messages are only available within an > extremely verbose HTML block, returned from getResponseBody(). It > would be a considerable convenience if those error or status messages > were also returned as simple strings, in getMessage() or otherwise. > > There's no good reason a developer using a Java-based API should have > to write custom code to parse an HTML block just to get back a > reasonable error message from an Exception in the GData API (including > service-specific subset APIs like that for Google Calendar). > > Right now, it seems each developer has to reinvent the wheel to do so, > whether they use HTML-specific tools, run the block through Tidy and > parse it as XML, parse it via regular expressions, or some other means. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Calendar 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-calendar-help-dataapi?hl=en -~----------~----~----~----~------~----~------~--~---
