<?xml version="1.0" encoding="ISO-8859-1"?>











<rss version="2.0">
  <channel>
    <title>The Java(tm) Specialists' Newsletter</title>
    <link>http://www.javaspecialists.eu</link>
    <description>The Java(tm) Specialists' Newsletter features advanced
articles and tips surrounding the Java Programming Language</description>
    <language>en</language>
    <copyright>Copyright 2000-2005, Dr Heinz Max Kabutz</copyright>
    <managingEditor>Dr Heinz Kabutz</managingEditor>
    <webMaster>Dr Heinz Kabutz</webMaster>
    <ttl>1440</ttl>

    
    <item>
      <title>Exceptions in Java
      </title>
      <link>http://www.javaspecialists.eu/archive/Issue162.html
      </link>
      <pubDate>Tue, 10 Jun 2008 00:00:00 GMT
      </pubDate>
      <description>In this article, we look at exception handling in Java. We
      start with the history of exceptions, looking back at the
      precursor of Java, a language called Oak. We see reasons
      why Thread.stop() should not be used and discover the
      mystery of the RuntimeException name. We then look at some
      best practices that you can use for your coding, followed
      by some worst practices, in the form of exception
      anti-patterns.
      </description>
    </item>
    
    <item>
      <title>Of Hacking Enums and Modifying "final static" Fields
      </title>
      <link>http://www.javaspecialists.eu/archive/Issue161.html
      </link>
      <pubDate>Fri, 23 May 2008 00:00:00 GMT
      </pubDate>
      <description>The developers of the Java language tried their best to
      stop us from constructing our own enum instances.  However,
      for testing purposes, it can be useful to temporarily add
      new enum instances to the system.  In this newsletter we
      show how we can do this using the classes in sun.reflect.
      In addition, we use a similar technique to modify static
      final fields, which we need to do if we want the switch
      statements to still work with our new enums.
      </description>
    </item>
    
    <item>
      <title>The Law of the Uneaten Spinach
      </title>
      <link>http://www.javaspecialists.eu/archive/Issue160.html
      </link>
      <pubDate>Mon, 12 May 2008 00:00:00 GMT
      </pubDate>
      <description>Imagine a very stubborn father insisting that his equally
      stubborn child eat its spinach before going to sleep.  In
      real life one of the "threads" eventually will give up, but
      in Java, the threads become deadlocked, with neither giving
      an inch.  In this newsletter we discover how we can
      sometimes escape from such deadlocked situations in Java
      and learn why the stop() function should never ever ever be
      called.
      </description>
    </item>
    
    <item>
      <title>The Law of Sudden Riches
      </title>
      <link>http://www.javaspecialists.eu/archive/Issue159.html
      </link>
      <pubDate>Mon, 5 May 2008 00:00:00 GMT
      </pubDate>
      <description>We all expect faster hardware to make our code execute
      faster and better.  In this newsletter we examine why this
      is not always true.  Sometimes the code breaks on faster
      servers or executes slower than on worse hardware.
      </description>
    </item>
    
  </channel>
</rss> 
 