Geek Answers Handbook

Moving from Java1.5 to Java 1.6?

I am currently running my web application on Java1.5 codebase, running it on Tomcat 5.5 and MySql 5. Looking at the list of add-ons added in Java1.6, I should ask the question: "Is there any good reason to go from 1, 5 to 1.6? " It seems incredible the lack of necessary improvements and additions. A lot of changes in Swing (not so interesting). Keep in mind that the current web application is stable (-ish) and moving the version always entails some risk.

Did I miss something important without moving? Is there a good reason to move up?

+4
source share
6 answers

Faster lead time. Improved dynamic debugging. Better look in Swing (not important for web applications). Supported in Windows Vista (may become important, depending on your platform).

JavaScript is integrated into the platform (it can be a big problem if you upgrade your webapp). Better scripting language support (can deploy RoR if necessary). Lightweight web services platform integrated (may be useful). Better already integrated support for JDBC4.

In other words, it depends, but overall enough to make a convincing argument. There is also enough that you can not use to make a convincing argument to the counter.

In the end you have to change. When you do this, if you have made the counter argument too long, you must eliminate several historical problems that have accumulated at once. This can overwhelm the team, so sometimes it’s better to remain “a little behind” the current, but never very outdated.

I assume that you have viewed the page, and if you have not done so, you should.

+4
source

Java 5 went " end of life " in 2009.

+4
source

The new VM is faster.

+1
source

Sun (now Oracle). On October 5, 2009, Java 5 reached the end-of-service status . " This means that Oracle will no longer fix bugs and security fixes unless you pay for the Java SE for Business contract (see the web page for details).

In addition, Java 6 contains many performance improvements (which may or may not be important for your specific application).

+1
source

It is usually easier to keep the application up to date if you stay in the latest version. (Not a bleeding edge, but a current).

Moving between 1.5 and 1.7 may require more work than if you first make the transition to 1.6.

0
source

jvisualvm in the JDK is reason enough to upgrade. Allows you to research and profile an already running process without any preparation.

0
source

More articles:


All Articles