Newsletter sign-up
View all newsletters

Enterprise Java Newsletter
Stay up to date on the latest tutorials and Java community news posted on JavaWorld

Sponsored Links

Optimize with a SATA RAID Storage Solution
Range of capacities as low as $1250 per TB. Ideal if you currently rely on servers/disks/JBODs

Client-side Java's evolutionary leap

Looking back on a year of changes

  • Print
  • Feedback

Page 3 of 6

Java SE 6u10 and 6u11

It's a well-known fact that the Java client platform has for years suffered limitations that have made it a less desirable alternative to competitors such as Flash and Silverlight. For example, the entire Java Runtime Environment (JRE) must be present before an applet or Java Web Start application starts running. JREs keep getting bigger (JRE 6 exceeds 14 MB), so download times keep lengthening. To address this limitation and others, Sun engineers conceived of Java SE 6u10 (called the Consumer JRE when the early-access version came out in 2007, then Java SE 6uN). A beta version debuted in April 2008, and the final release was in October.

The following technologies in Java SE 6u10 help overcome JRE limitations:

  • Java Deployment Toolkit: Simplifies the task of deploying applets and applications to a variety of clients. It consists of a JavaScript file and a browser plugin that make it possible to install a JRE automatically.
  • Java Kernel: Lets first-time Java users run applets and applications faster by downloading only that part of the JRE needed to run the applet/application immediately. Then it downloads the rest of the JRE in the background.
  • Java Quick Starter: Prefetches portions of the JRE into a memory cache, greatly reducing the average Java Platform cold startup time (the time to launch a Java applet or application for the first time following a computer reboot).
  • New Java Plugin: Improves reliability by running applets in operating-system processes separate from the browser. If an applet fails, the browser is unaffected. Other improvements include each applet being able to increase its heap size, and improved Java-JavaScript communication.

Java SE 6u10 also includes bug fixes, Nimbus (which modernizes Java's cross-platform look and feel), a new graphics pipeline that uses Direct3D to accelerate Java2D graphics primitives on Windows, and support for translucent/shaped windows.

In December, Sun released Java SE 6u11. It focuses on security and bug fixes. A new download engine works with 6u10's patch-in-place strategy (future JRE updates are applied in the existing JRE directory so that only changed files need to be downloaded) to reduce the size of future updates. To avoid interfering with a user's Internet usage, this engine monitors that usage and throttles back its own bandwidth.

JavaFX Preview SDK and SDK 1.0

JavaFX was a source of both excitement and dismay in 2008, with three especially striking highlights. First, then-Sun employees Hans Muller and Chet Haase gave developers a peek into the Java-based scene graph and animation frameworks that would support JavaFX via Muller's Introducing the SceneGraph Project and Haase's  Been There, Scene That, Part 1 and Part 2 blog posts.

Second was the launch of the JavaFX Preview SDK on July 31. It provided a JavaFX plugin for NetBeans 6.1, which let you easily compile scripts from the IDE. The Preview SDK also provided Project Nile, whose Adobe Illustrator and Photoshop plugins made it easy for content designers to export their designs to JavaFX developers.

  • Print
  • Feedback

Resources

Also from JavaWorld