{"id":62,"date":"2008-10-23T18:04:00","date_gmt":"2008-10-23T17:04:00","guid":{"rendered":"http:\/\/jimblackler.com\/blog\/?p=62"},"modified":"2008-10-23T18:06:05","modified_gmt":"2008-10-23T17:06:05","slug":"viewing-raw-xml-traffic-when-using-google-data-java-client-apis","status":"publish","type":"post","link":"https:\/\/jimblackler.com\/?p=62","title":{"rendered":"Viewing raw XML traffic when using Google Data Java Client APIs"},"content":{"rendered":"

The Google Data Java Client APIs provide a convenient way for Java prorgams to interface with Google’s public Data APIs, for Google calendars, contacts, and many other services.<\/p>\n

It’s such a good abstraction, however, there is no clear way of seeing the underlying XML of the feed. When debugging, and for their interest, programmers may wish to see this data – it’s supposed to be human-readable after all.<\/p>\n

After at least an hour of playing around I found the commands to enable the logging in the client’s initialization. Traffic will then be output to the console at run time.<\/p>\n

The gotcha is that enabling verbose output on Java’s logging requires not just the logs to be set to Level.ALL, but also the underlying handlers.<\/p>\n

Here’s the code.<\/p>\n

\n\n\t\n\t
\n\t\t
  1. import<\/span> java.util.logging.Logger<\/span>;<\/span><\/div><\/li>\n
  2. import<\/span> com.google.gdata.client.http.GoogleGDataRequest<\/span>;<\/span><\/div><\/li>\n
  3. import<\/span> com.google.gdata.client.http.HttpGDataRequest<\/span>;<\/span><\/div><\/li>\n<\/ol>\t<\/div>\n\n<\/div>\n\n
    \n\n\t\n\t
    \n\t\t
    1. Logger.getLogger<\/span>(<\/span>Logger.GLOBAL_LOGGER_NAME<\/span>)<\/span>.getParent<\/span>(<\/span>)<\/span>.getHandlers<\/span>(<\/span>)<\/span>[<\/span>0<\/span>]<\/span>.setLevel<\/span>(<\/span>Level.ALL<\/span>)<\/span>;<\/span><\/div><\/li>\n
    2. Logger.getLogger<\/span>(<\/span>GoogleGDataRequest.class<\/span>.getName<\/span>(<\/span>)<\/span>)<\/span>.setLevel<\/span>(<\/span>Level.ALL<\/span>)<\/span>;<\/span><\/div><\/li>\n
    3. Logger.getLogger<\/span>(<\/span>HttpGDataRequest.class<\/span>.getName<\/span>(<\/span>)<\/span>)<\/span>.setLevel<\/span>(<\/span>Level.ALL<\/span>)<\/span>;<\/span><\/div><\/li>\n<\/ol>\t<\/div>\n\n<\/div>\n\n","protected":false},"excerpt":{"rendered":"

      The Google Data Java Client APIs provide a convenient way for Java prorgams to interface with Google’s public Data APIs, for Google calendars, contacts, and many other services. It’s such a good abstraction, however, there is no clear way of seeing the underlying XML of the feed. When debugging, and for their interest, programmers may […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-62","post","type-post","status-publish","format-standard","hentry","category-general-programming"],"_links":{"self":[{"href":"https:\/\/jimblackler.com\/index.php?rest_route=\/wp\/v2\/posts\/62","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jimblackler.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jimblackler.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jimblackler.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/jimblackler.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=62"}],"version-history":[{"count":0,"href":"https:\/\/jimblackler.com\/index.php?rest_route=\/wp\/v2\/posts\/62\/revisions"}],"wp:attachment":[{"href":"https:\/\/jimblackler.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=62"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jimblackler.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=62"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jimblackler.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=62"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}