<?xml version="1.0" encoding="iso-8859-1"?>

<rdf:RDF
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
  xmlns:admin="http://webns.net/mvcb/"
  xmlns:cc="http://web.resource.org/cc/"
  xmlns="http://purl.org/rss/1.0/">

<channel rdf:about="http://blogs.codehaus.org/people/joehni//archives/coding.html">
<title>Joerg talks to himself - Coding</title>
<link>http://blogs.codehaus.org/people/joehni//archives/coding.html</link>
<description></description>
<dc:language>en-us</dc:language>
<dc:creator></dc:creator>
<dc:date>2008-01-19T08:14:44+01:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=2.661" />

<items>
<rdf:Seq><rdf:li rdf:resource="http://blogs.codehaus.org/people/joehni/archives/001651_write_once_run_anywhere.html" />
<rdf:li rdf:resource="http://blogs.codehaus.org/people/joehni/archives/001500_fooled_by_java_identity.html" />
</rdf:Seq>
</items>

</channel>

<item rdf:about="http://blogs.codehaus.org/people/joehni/archives/001651_write_once_run_anywhere.html">
<title>Write once run anywhere??</title>
<link>http://blogs.codehaus.org/people/joehni/archives/001651_write_once_run_anywhere.html</link>
<description><![CDATA[<p>I've always been a big fan of Java, especially since its promise "Write once, run everywhere" comes very close - at least if you compare the situation with the C/C++ world 8 years ago (and take all the libraries into account).</p>

<p>However, this promise nearly killed my Christmas last year. Ever used the new fancy ScheduledThreadPoolExecutor? Nice class. Easy task handling in a multi-threaded application design (at least if you dont try to extend it, but this is another story). I've developed my application on Windows, we did extensive tests in a Linux environment and when we delivered the application to our customer's location Friday before Christmas it crashed quite instantly. Within the logger! What's that?</p>]]></description>
<dc:subject>Coding</dc:subject>
<dc:creator>Jörg Schaible</dc:creator>
<dc:date>2008-01-19T08:14:44+01:00</dc:date>
</item>
<item rdf:about="http://blogs.codehaus.org/people/joehni/archives/001500_fooled_by_java_identity.html">
<title>Fooled by Java identity</title>
<link>http://blogs.codehaus.org/people/joehni/archives/001500_fooled_by_java_identity.html</link>
<description><![CDATA[<p>How often do you imply facts that nowhere have been stated or confirmed? Last week I found myself trapped by such a certainty that revealed to be a false assumption.</p>

<p>Ever asked yourself what you can expect from the values delievered by the JDK's method <code>System.identityHashCode(Object object)</code>? My original believe (and I suppose I am not alone here) was that the value reflects somehow the memory address of the given object. Not that I tried to access the object in any obscure way, it was just based on the fact that there are not a lot of more things to assign an identity to an object - implying that identity has something to do with uniqueness for the object's lifetime.</p>]]></description>
<dc:subject>Coding</dc:subject>
<dc:creator>Jörg Schaible</dc:creator>
<dc:date>2007-01-27T14:55:22+01:00</dc:date>
</item>


</rdf:RDF>
