<?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>Chaotic Java &#187; Java</title>
	<atom:link href="http://chaoticjava.com/posts/category/code/java-language/feed/" rel="self" type="application/rss+xml" />
	<link>http://chaoticjava.com</link>
	<description>The internet, design patterns, frameworks and Java</description>
	<lastBuildDate>Mon, 14 Nov 2011 03:49:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Avoiding getter and setter pairs in GWT&#8217;s RequestFactory</title>
		<link>http://chaoticjava.com/posts/avoiding-getter-and-setter-pairs-in-gwt-requestfactory/</link>
		<comments>http://chaoticjava.com/posts/avoiding-getter-and-setter-pairs-in-gwt-requestfactory/#comments</comments>
		<pubDate>Mon, 05 Sep 2011 18:40:16 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Google Web Toolkit]]></category>
		<category><![CDATA[chain of responsibility]]></category>
		<category><![CDATA[code]]></category>
		<category><![CDATA[gwt]]></category>
		<category><![CDATA[requestfactory]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/?p=394</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/avoiding-getter-and-setter-pairs-in-gwt-requestfactory/";</script>GWT (Google web toolkit) is a great development toolkit for web applications. I&#8217;ve been following it for a white now (including two somehwat popular posts about drag and drop and about enums, back when those weren&#8217;t so popular..) and it keeps getting better and better. Recently, in version 2.1, they&#8217;ve added something called the RequestFactory, [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/avoiding-getter-and-setter-pairs-in-gwt-requestfactory/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Tweaking the producer-consumer model</title>
		<link>http://chaoticjava.com/posts/producer-consumer-model/</link>
		<comments>http://chaoticjava.com/posts/producer-consumer-model/#comments</comments>
		<pubDate>Fri, 29 Oct 2010 21:53:49 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Design Patterns]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Self Ideas]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/?p=362</guid>
		<description><![CDATA[The makes a few assumptions in order to work. In this post I’ll discuss some of these assumptions, what happens when they break, and a cool solution to deal with it. The two assumptions I’d like to discuss are: "All producers are equal" and "Once sent to the queue, a producer doesn’t care about its products".
]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/producer-consumer-model/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>Revival of the Yielder project?</title>
		<link>http://chaoticjava.com/posts/revival-of-the-yielder-project/</link>
		<comments>http://chaoticjava.com/posts/revival-of-the-yielder-project/#comments</comments>
		<pubDate>Sat, 08 Aug 2009 21:17:00 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Framework Development]]></category>
		<category><![CDATA[Yielder]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/?p=314</guid>
		<description><![CDATA[After not touching the yielder project for a long time, I decided to go back and make the change I knew I needed but feared of doing and fix the yielder project.
]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/revival-of-the-yielder-project/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Simple solution to resource collection</title>
		<link>http://chaoticjava.com/posts/simple-solution-to-resource-collection/</link>
		<comments>http://chaoticjava.com/posts/simple-solution-to-resource-collection/#comments</comments>
		<pubDate>Mon, 03 Aug 2009 21:24:24 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Frameworks]]></category>
		<category><![CDATA[Self Ideas]]></category>
		<category><![CDATA[Tiger]]></category>
		<category><![CDATA[gc]]></category>
		<category><![CDATA[io]]></category>
		<category><![CDATA[resources]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/?p=301</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/simple-solution-to-resource-collection/";</script>It&#8217;s called garbage collection, not resource collection! Java&#8217;s garbage collector has made life so easy for us developers that we sometimes confuse between deleting a reference, i.e. a task the GC does, and releasing a resource &#8211; a task the GC doesn&#8217;t do. That&#8217;s because the GC does something else for us called object finalization, [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/simple-solution-to-resource-collection/feed/</wfw:commentRss>
		<slash:comments>8</slash:comments>
		</item>
		<item>
		<title>The quiet revolution &#8211; Part I: JSR 296</title>
		<link>http://chaoticjava.com/posts/the-quiet-revolution-part-i-jsr-296/</link>
		<comments>http://chaoticjava.com/posts/the-quiet-revolution-part-i-jsr-296/#comments</comments>
		<pubDate>Fri, 02 Jan 2009 18:32:16 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[JDK7]]></category>
		<category><![CDATA[gui]]></category>
		<category><![CDATA[jsr-296]]></category>
		<category><![CDATA[opinion]]></category>
		<category><![CDATA[swing]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/?p=261</guid>
		<description><![CDATA[JSR 296 brings a "Swing for the rest of us" approach for Swing application development.]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/the-quiet-revolution-part-i-jsr-296/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Jsr-292&#8242;s first draft &#8211; a late review</title>
		<link>http://chaoticjava.com/posts/jsr-292-first-draft-review/</link>
		<comments>http://chaoticjava.com/posts/jsr-292-first-draft-review/#comments</comments>
		<pubDate>Fri, 19 Dec 2008 18:51:08 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[invokedynamic]]></category>
		<category><![CDATA[Java]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/?p=249</guid>
		<description><![CDATA[Being fashionably late as always, I read the JSR-292's early draft and had some comments on it]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/jsr-292-first-draft-review/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Build.xml generator for Eclipse</title>
		<link>http://chaoticjava.com/posts/buildxml-generator-for-eclipse/</link>
		<comments>http://chaoticjava.com/posts/buildxml-generator-for-eclipse/#comments</comments>
		<pubDate>Sat, 19 Jul 2008 21:01:22 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Eclipse]]></category>
		<category><![CDATA[Not Code]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/?p=238</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/buildxml-generator-for-eclipse/";</script>Know the feeling when you&#8217;re just about to release code to the public&#8217;s eye, and all you need to do is write that pesky build file?Â Even as I write it I feel it&#8217;s an understatement: the task of creating an ant build file can take a few good days out of anyone&#8217;s life, and even [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/buildxml-generator-for-eclipse/feed/</wfw:commentRss>
		<slash:comments>12</slash:comments>
		</item>
		<item>
		<title>Switch by class type</title>
		<link>http://chaoticjava.com/posts/switch-by-class-type/</link>
		<comments>http://chaoticjava.com/posts/switch-by-class-type/#comments</comments>
		<pubDate>Sat, 24 May 2008 04:46:52 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Self Ideas]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/?p=230</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/switch-by-class-type/";</script>Imagining a method which receives as a parameter a type Object instance and needs to perform some action according to its type is not difficult. In fact, there are several design patterns that, when used in combination, help solve just that. However, this post is about adding a new switch..case construct to prevent some boiler-plate [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/switch-by-class-type/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
		<item>
		<title>Exposing collections: paranoia vs trust approaches</title>
		<link>http://chaoticjava.com/posts/exposing-collections-paranoia-vs-trust-approaches/</link>
		<comments>http://chaoticjava.com/posts/exposing-collections-paranoia-vs-trust-approaches/#comments</comments>
		<pubDate>Mon, 19 May 2008 06:17:35 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[thoughts]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/?p=236</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/exposing-collections-paranoia-vs-trust-approaches/";</script>Whenever a class in my model contains a collection which requires that particular care be taken with its items, there&#8217;s an internal debate regarding how to expose it to other classes. And with this, there are two major schools: one, the paranoia-based approach which doesn&#8217;t allow external code to touch the collection&#8217;s internal items and [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/exposing-collections-paranoia-vs-trust-approaches/feed/</wfw:commentRss>
		<slash:comments>16</slash:comments>
		</item>
		<item>
		<title>Giving a break for cleaner code</title>
		<link>http://chaoticjava.com/posts/giving-a-break-for-cleaner-code/</link>
		<comments>http://chaoticjava.com/posts/giving-a-break-for-cleaner-code/#comments</comments>
		<pubDate>Thu, 01 May 2008 05:42:35 +0000</pubDate>
		<dc:creator>Aviad</dc:creator>
				<category><![CDATA[Language]]></category>

		<guid isPermaLink="false">http://chaoticjava.com/?p=226</guid>
		<description><![CDATA[<script type="text/javascript">dzone_url = "http://chaoticjava.com/posts/giving-a-break-for-cleaner-code/";</script>Time for some refreshing the memory with a Java language feature probably few use, and maybe for a good reason. Suppose you&#8217;re running code on elements of an array up until a certain element is found. When your code finds that element, it stops the iteration. Therefore, your code might look like the following: for [...]]]></description>
		<wfw:commentRss>http://chaoticjava.com/posts/giving-a-break-for-cleaner-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

