There has been talk recently that Sun is planning to end the use of the J2 platform name and branding scheme. The proposal is that the terms Java Enterprise Edition and Java Standard Edition will replace J2EE and J2SE. If you had the opportunity to read the March edition of JDJ, you will have discovered that the history of the J2 name, although not perfect, was a compromise by recognizing the platform had taken a significant step forward and resisting the temptation for calling the new release Java 2000.
Given that history, a name change was probably always on the cards but there was never a good time to make that change. In the early days of J2EE, getting vendors to adopt and use the term J2EE was essential for the success of the platform as an industry-wide event. Changing the J2EE name at that point would have confused matters to no end, so a name change was a nonstarter. Later, with the emergence of the .NET Framework from Microsoft, the Java community rallied behind the J2EE banner when comparing the two platforms. Microsoft even used this comparison, partly in an attempt to validate a very new .NET platform, even to the extent of focusing less on the comparison of Java versus C#.
Why change one of the most successful brands now? Only the marketing teams at Sun know the real answer. The J2SE name in particular never got the industry recognition that J2EE received, but changing all the brands for consistency is never cheap. What it means for the average Java developer is unclear. It is now more descriptive to say that you are a Java Enterprise Edition developer, but at the same time clients and recruiters will still be looking for a J2EE developers so I doubt the J2EE name will ever really disappear.
Regardless if you call yourself a J2EE or Java Enterprise Edition developer, there were two other pieces of interesting news this month. The first was another article from Sun about the Barcelona project (the Multi-Tasking Virtual Machine, MVM); the second item was the first shipping Java system from Azul Systems.
The Multi-Tasking Virtual Machine
The MVM JVM is still a research project but garners a lot of attention in and outside Sun. The claims are that using the MVM technology will result in more scalable JVMs with improved startup time. The version I tried at Sun didn't use the standard isolated JSR and I didn't get very far making it work on Solaris. The MVM model is similar to other service style models like the X-based console/terminal service. The X-based console service does not start a new process each time a terminal request is received but instead spins off a new instance. The huge advantage is decreased startup time; the traditional downside is that if one console experiences an error, it can take down all the other running consoles - something that was very frustrating for early users. The MVM plan is to spin off applications that would be a higher risk, for example, using JNI in their own process space. We will have to wait to see a public download, but getting a product from research into production is hard and requires a lot of dedication.
