<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Software Steeplechase Comments</title>
	<link>http://steep.blogsome.com</link>
	<description>Hayden Steep's development obstacle course. (Java, JEE, and beyond)</description>
	<pubDate>Wed, 18 Nov 2009 17:07:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: Web developer</title>
		<link>http://steep.blogsome.com/2006/10/25/creating-a-servlet-with-a-self-contained-web-server/#comment-13</link>
		<pubDate>Thu, 20 Aug 2009 14:21:21 +0100</pubDate>
		<guid>http://steep.blogsome.com/2006/10/25/creating-a-servlet-with-a-self-contained-web-server/#comment-13</guid>
					<description>Cool,

Great article ,I like it that it is step by step

Anyway, thanks for the post</description>
		<content:encoded><![CDATA[	<p>Cool,</p>
	<p>Great article ,I like it that it is step by step</p>
	<p>Anyway, thanks for the post</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Ian Heffernan</title>
		<link>http://steep.blogsome.com/2006/10/25/creating-a-servlet-with-a-self-contained-web-server/#comment-12</link>
		<pubDate>Fri, 29 Jun 2007 04:37:00 +0100</pubDate>
		<guid>http://steep.blogsome.com/2006/10/25/creating-a-servlet-with-a-self-contained-web-server/#comment-12</guid>
					<description>If you had a normal Java Swing gui and the browser inside, how would you communicate between the swing app and the browser. E.g Say you wanted to save some form details using a menu file|save option. Or would it be better to have the menu within your JSP/Servlet??</description>
		<content:encoded><![CDATA[	<p>If you had a normal Java Swing gui and the browser inside, how would you communicate between the swing app and the browser. E.g Say you wanted to save some form details using a menu file|save option. Or would it be better to have the menu within your JSP/Servlet??</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hayden</title>
		<link>http://steep.blogsome.com/2006/10/04/comskip-monitor-a-java-service/#comment-9</link>
		<pubDate>Wed, 04 Oct 2006 16:21:33 +0100</pubDate>
		<guid>http://steep.blogsome.com/2006/10/04/comskip-monitor-a-java-service/#comment-9</guid>
					<description>Thanks for the tip Curt.  ProcessBuilder looks slightly more elegant than having to use the Runtime class.  The SageTV software I use states Java 1.4.x as a requirement, so I targeted my code to that version.  Maybe I can switch over to ProcessBuilder in a future release.</description>
		<content:encoded><![CDATA[	<p>Thanks for the tip Curt.  ProcessBuilder looks slightly more elegant than having to use the Runtime class.  The SageTV software I use states Java 1.4.x as a requirement, so I targeted my code to that version.  Maybe I can switch over to ProcessBuilder in a future release.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Curt Cox</title>
		<link>http://steep.blogsome.com/2006/10/04/comskip-monitor-a-java-service/#comment-8</link>
		<pubDate>Wed, 04 Oct 2006 16:12:33 +0100</pubDate>
		<guid>http://steep.blogsome.com/2006/10/04/comskip-monitor-a-java-service/#comment-8</guid>
					<description>If you can use Java 5+, you will probably want to look at ProcessBuilder instead of Runtime.exec().</description>
		<content:encoded><![CDATA[	<p>If you can use Java 5+, you will probably want to look at ProcessBuilder instead of Runtime.exec().</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Don Shade</title>
		<link>http://steep.blogsome.com/2006/07/13/why-the-java-compiler-enforces-catching-some-exceptions-and-not-others/#comment-7</link>
		<pubDate>Wed, 19 Jul 2006 12:09:10 +0100</pubDate>
		<guid>http://steep.blogsome.com/2006/07/13/why-the-java-compiler-enforces-catching-some-exceptions-and-not-others/#comment-7</guid>
					<description>Those very smart people seem to agree that checked exceptions are not needed.  I'm not sure why (maybe I'm not as smart), but it seems to be a healthy reminder that Eclipse will force a try/catch block or a throws clause.   

If I were writing a database application and I knew there was a possible SQLException, I would write graceful handling code for this and a finally block for closing the connection to avoid connection pool leaks.

But when it comes to file system exceptions (like file system full, etc.) there's not much I, as a Java programmer, want to do about this, so I would not &quot;check&quot; for those exceptions.

My comments may seem trite.  However, I've attended many Java User Group presentations where this topic is discussed and debated.
  </description>
		<content:encoded><![CDATA[	<p>Those very smart people seem to agree that checked exceptions are not needed.  I&#8217;m not sure why (maybe I&#8217;m not as smart), but it seems to be a healthy reminder that Eclipse will force a try/catch block or a throws clause.   </p>
	<p>If I were writing a database application and I knew there was a possible SQLException, I would write graceful handling code for this and a finally block for closing the connection to avoid connection pool leaks.</p>
	<p>But when it comes to file system exceptions (like file system full, etc.) there&#8217;s not much I, as a Java programmer, want to do about this, so I would not &#8220;check&#8221; for those exceptions.</p>
	<p>My comments may seem trite.  However, I&#8217;ve attended many Java User Group presentations where this topic is discussed and debated.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
