<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Javablog &#187; Google</title>
	<atom:link href="http://javablog.co.uk/category/google/feed/" rel="self" type="application/rss+xml" />
	<link>http://javablog.co.uk</link>
	<description>by Java coders, for Java coders</description>
	<lastBuildDate>Mon, 04 Jan 2010 15:20:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Reducing Java Boilerplate</title>
		<link>http://javablog.co.uk/2009/10/20/reducing-java-boilerplate/</link>
		<comments>http://javablog.co.uk/2009/10/20/reducing-java-boilerplate/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 22:24:38 +0000</pubDate>
		<dc:creator>Sam</dc:creator>
				<category><![CDATA[Google]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[NetBeans]]></category>

		<guid isPermaLink="false">http://javablog.co.uk/?p=187</guid>
		<description><![CDATA[One of the darker sides of Java is the boilerplate; lines and lines of boring, repetitious and ugly boilerplate. In this post, we show how to reduce/hide boilerplate and increase the readability of your Java code under the following circumstances: argument checking, with exception throwing equals and hashCode providing getters and setters (the JavaBean pattern) [...]]]></description>
		<wfw:commentRss>http://javablog.co.uk/2009/10/20/reducing-java-boilerplate/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Android&#8230; what J2ME should have been</title>
		<link>http://javablog.co.uk/2007/11/12/android-what-j2me-should-have-been/</link>
		<comments>http://javablog.co.uk/2007/11/12/android-what-j2me-should-have-been/#comments</comments>
		<pubDate>Mon, 12 Nov 2007 20:02:42 +0000</pubDate>
		<dc:creator>Sam</dc:creator>
				<category><![CDATA[Android]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[J2ME]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[OSS]]></category>
		<category><![CDATA[SDK]]></category>

		<guid isPermaLink="false">http://javablog.co.uk/2007/11/12/android-what-j2me-should-have-been/</guid>
		<description><![CDATA[Google released Android today, the Java SDK that people have been calling the gPhone&#8230; and wow! It&#8217;s what J2ME should have been, or at least what it should have turned into. For a start, it has Java 5 language features such as generics and annotations&#8230; features that help the developer but add no additional burden [...]]]></description>
		<wfw:commentRss>http://javablog.co.uk/2007/11/12/android-what-j2me-should-have-been/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Google Web Toolkit</title>
		<link>http://javablog.co.uk/2007/09/01/google-web-toolkit/</link>
		<comments>http://javablog.co.uk/2007/09/01/google-web-toolkit/#comments</comments>
		<pubDate>Sat, 01 Sep 2007 15:33:09 +0000</pubDate>
		<dc:creator>Sam</dc:creator>
				<category><![CDATA[Ajax]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[GWT]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Javascript]]></category>
		<category><![CDATA[Servlets]]></category>
		<category><![CDATA[Tomcat]]></category>

		<guid isPermaLink="false">http://javablog.co.uk/2007/09/01/google-web-toolkit/</guid>
		<description><![CDATA[We recently discovered the wonderful world of the Google Web Toolkit. In a nutshell, GWT lets you write Javascript/AJAX applications entirely in Java. You write client code in a subset of Java 1.4, making use of a really big library of existing widgets, which is then compiled into Javascript. Server side uses the standard Servlet [...]]]></description>
		<wfw:commentRss>http://javablog.co.uk/2007/09/01/google-web-toolkit/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

