Easy Deployment is Finally Here

This session mainly covered Java JRE deployments necessary for consumers to run applications. These issues are not relevant with server-based web applications but do exist with applets or client-applications. Issues today range from understanding what JRE a consumer has installed (or doesn't) to simplifying and speeding the installation process.

Currently, some Javascript scripts are available to detect a JRE version but they do not cover all browser versions. Also, these scripts cannot obtain an exact version, such as JRE 1.4_2. If outside the browser, an installation usually needs to check the registry. Plus, even the current JRE installer can use improvements.

The next generation installer will be more-attractive, have better and easier instructions, active messaging (messages/information during install). These are simple changes but important. Also, the next installer will replace the current JRE rather than continuing to install new JRE's.

Sun will be providing a Java Technology Deployment Toolkit (JTDT) in the future. The toolkit will provide a few alternatives in ensuring the proper JRE version is installed. Javascript (JS) files will contain script that is cross-browser compatible. The JS will contain methods to return a list of installed JRE versions, check for a specific JRE version, and install the latest JRE version. Another JS method will create necessary applet tags after checking and installing, if necessary, a JRE. However, limitation to this approach is the JRE installation is not seamless, only the highest JRE version can be detected, and a family version is detected (JRE 1.5 vs. 1.5_1). Therefore, upcoming JRE's will include a browser plugin that performs the same Javascript code but using native code. This will allow more fine-grain analysis to be done (and maybe improve the install???).

The last offering in the JTDT is a set of executables to easy a non-web application. A 'GetJava.exe" executable can detect JRE versions and install them. These executables are intended to be placed in an installer.

Improvements to decrease the size of the JRE (~12 MB) are being done. A JRE will be modularized and only contain enough code to run a "Hello World" output when standalone. Other functionality and needed classes will be downloaded on demand. Note, the full JRE installer will still be available. A client application will not need to be coded differently as the updates will automatically be performed. Plus, some mechanism will be available at startup if an application wants to ensure necessary "components" are installed.