Comments on: Is it time for Java 5? http://blog.punchbarrel.com/2008/09/21/is-it-time-for-java-5/ Frank Carver's musings about software and life Mon, 08 Mar 2010 13:52:05 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: blog.stringtree.org » Blog Archive » Java 6 breaks JDBC http://blog.punchbarrel.com/2008/09/21/is-it-time-for-java-5/comment-page-1/#comment-204 blog.stringtree.org » Blog Archive » Java 6 breaks JDBC Tue, 23 Sep 2008 10:36:49 +0000 http://blog.punchbarrel.com/2008/09/21/is-it-time-for-java-5/#comment-204 [...] all started with an innocuous question in a comment on my Punchbarrel blog. I had posted asking for opinions on a move to Java 5, potentially abandoning Java 1.4, for the [...] [...] all started with an innocuous question in a comment on my Punchbarrel blog. I had posted asking for opinions on a move to Java 5, potentially abandoning Java 1.4, for the [...]

]]> By: Frank http://blog.punchbarrel.com/2008/09/21/is-it-time-for-java-5/comment-page-1/#comment-198 Frank Mon, 22 Sep 2008 20:22:38 +0000 http://blog.punchbarrel.com/2008/09/21/is-it-time-for-java-5/#comment-198 The issue I think you are referring to is the way that Sun have broken some key interfaces within JDBC by adding new methods from other interfaces. This is extremely irritating, and an example of the thoughtlessness which has accompanied several Java versions. The whole point of an interface is that it should allow multiple implementations from multiple creators; changing an interface in a way which breaks existing implementations is plain stupid. I plan to work through the Stringtree code and implement as many of these new methods as I can while maintaining backward compatibility, even if I don't move the whole codebase to a new Java version. The issue I think you are referring to is the way that Sun have broken some key interfaces within JDBC by adding new methods from other interfaces.

This is extremely irritating, and an example of the thoughtlessness which has accompanied several Java versions. The whole point of an interface is that it should allow multiple implementations from multiple creators; changing an interface in a way which breaks existing implementations is plain stupid.

I plan to work through the Stringtree code and implement as many of these new methods as I can while maintaining backward compatibility, even if I don’t move the whole codebase to a new Java version.

]]> By: Harry Pynn http://blog.punchbarrel.com/2008/09/21/is-it-time-for-java-5/comment-page-1/#comment-196 Harry Pynn Mon, 22 Sep 2008 16:46:05 +0000 http://blog.punchbarrel.com/2008/09/21/is-it-time-for-java-5/#comment-196 Ditch 1.4. While you're at have you considered going straight to java 6? Can I currently use stringtree with java 6 if I'm using jdbc? Seem to recall some problem with the java DriverManager interface changing between 5 and 6. Maybe 2 different jars are needed - 1 for each of java 5 and 6? Ditch 1.4. While you’re at have you considered going straight to java 6? Can I currently use stringtree with java 6 if I’m using jdbc? Seem to recall some problem with the java DriverManager interface changing between 5 and 6. Maybe 2 different jars are needed – 1 for each of java 5 and 6?

]]>