Java Terms and VersionsJava Versions and Terminology DemystifiedThough Sun Microsystems and the other Java Community Process participants have built a marvelous platform for software development, they have not done such a fabulous job managing their buzzwords. There are not only many overlapping terms to understand -- Java, J2SE, Java SE, J2EE, Java EE, SDK, JDK, JRE, etc. -- there are multiple versions and, in fact, multiple version numbering systems in play. This document aims first to clarify the terms and the version numbers, and then offers some tips on which Java version(s) are most likely to be appropriate in training situations.
The frequently asked questionThe most common version question that occurs when considering Java training is simply, "Do I want Java 1.4 or Java 5?" The shortest answer we can manage to that question is here, though you may want to dig into other sections for details. After many revisions which only added new functionality to the Java standard APIs, the Java 5 release introduced a number of powerful new features to the Java language and runtime, especially improving ease of use and type safety. Since then there has been one more major release, which is Java 6; this is back in the mode of enhancing functionality without changing any basics of the language itself. Java 5/6 is clearly a superior tool, but because classes compiled with Java 5 won't work in older runtimes, there is a significant barrier to migration, and many companies will hold off on moving to Java 5 for months or even years. This means there is no simple, single answer to the question! The very best thing to do is to ask the client or the trainees themselves what version of Java they are or will soon be using, and train for that version. (But, see below for the distinction between Java SE and EE.) For a brief decision framework, see which version do I want?. What do the terms mean?First a quick explanation of terminology, in glossary form:
Which version is which?Within the Java SE -- again, this is the platform most people are referring to when they talk about Java software, unless they specifically mention Java EE -- there are a few things to know about version numbers. First, the Java language and the Java SE platform share a version number, so to say "Java 1.3" is to say "Java SE 1.3." Technically, one is the language and one is the platform, but they move in tandem. The "2" in "J2SE" looked like a version number of sorts, but it mostly confused the issue of what "version of Java" one was working with or wanted. The primary version numbering has historically run from Java 1.0 (released in 1996) up through 1.1, 1.2, 1.3, and 1.4; there have been minor upgrades to each platform along the way and so, for instance, many companies are currently using Java 1.4.2. As of Java 1.2, Sun defined the three-platform architecture and developed the "Java 2" platform as a brand of sorts. Thus -- sadly -- "Java 2" overlaps "Java 1.2," All versions since Java 1.2 have been versions of the "Java 2 Platform." Then, Java 1.5 was released, and the version-numbering scheme was also revised, with the aim of making the first digit in the number more meaningful: we'll start talking about version X, not version 1.X. So Java 1.5 is also Java 5! Fantastic; and 1.6 also equals 6. Either number is valid, but Sun generally favors 6 for the current version (and so does Capstone). Future revisions will just be labeled 7, 8, etc., with minor updates appearing as "update N." So these three overlapping schemes lay out like this:
Which version do I want?Java SE releases are backward-compatible, for the most part. However there is less forward compatibility. By "backward-compatible," we mean that old code will run on a new version of the platform; and by "forward-compatible," that code written on a new version of the platform will run on an old version of the platform. Especially with the new release of Java 5.0, there is no such forward-compatibility: this version uses a new format for its binary files (class files), which cannot be understood by an old (1.4 or earlier) runtime. Capstone offers multiple versions of many of its Java courses, but which version should you choose for training? It can be critical to get this right, as the language changed significantly between 1.4 and 5.0. If you are not sure, the first, best option is to contact someone in your company or at your client's site who knows. Typically there is either a Java infrastructure in place, or one is forming, or there is a specific product with specific requirements including a Java version. If you have a mixed classroom (perhaps a public offering) or simply don't know what the participants will want, here are a few guidelines and tips:
So there's a tradeoff in training situations. 1.4 coding techniques are valid for both 1.4 and 5.0 environments. 5.0 introduces some exciting new features that may give trainees a more valuable learning experience; but they may also learn skills that they can't apply if they are or will be working in a 1.4 context. |  |
