Your search did not match any results.
We suggest you try the following to help find what you’re looking for:
Java TM Web Start Technology Version 1.2
This document describes the new features, enhancements, and bug fixes that were made for this release of Java TM Web Start software.
With the new auto installation feature, users who don't have Java Web Start will be prompted to download Java Web Start from JSC. They will click through one security dialog box, which will automatically initiate a download of either Java Web Start alone or Java Web Start plus Java Runtime Environment 1.4.1, depending on how the developer has set up the application's web page.
When the download is complete, Java Web Start (and the Java Runtime Environment, if it was downloaded) will be automatically installed on the user's machine, and then Java Web Start will launch the application.
Note -- This feature is available only for Microsoft Windows platforms.
iconelement with a
kind="splash"attribute to the application's JNLP file. For example, the following element would indicate that the image contained in the file
MyIcon.gifshould be displayed as a "splash" image during application launch.
<icon kind="splash" href="/javase/technologies/desktop/javawebstart/1.2/docs/MyIcon.gif"/>
Splash image files can be either GIF or JPEG format. As with all icon elements, the
href attribute for a splash image can be either an absolute or relative URL. If relative, it is relative to the URL specified in the JNLP file's
If the JNLP file does not contain an
icon tag with a
kind="splash" attribute, but does contain another
icon tag, Java Web Start will display a splash screen consisting of the image specified by the
icon element on the left and the application's title and vendor on the right. The title and vendor are taken from the
vendor tags in the JNLP file. Here is an example splash screen of this sort for the Draw application demo.
If the JNLP file does not contain any
icon tags, the splash image will consist of the application's title and vendor, as taken from the JNLP file.
Splash images will be surrounded by a border defined by Java Web Start.
The first time an application is launched following the addition or modification of the
icon element in the JNLP file, the old splash image will still be displayed. The new splash image will appear on the second and subsequent launches of the application.
Specify a non-UTF-8 encoding in the XML prolog of the JNLP file. For example, the following line indicates that the JNLP file will be encoded in UTF-16.
<?xml version="1.0" encoding="utf-16"?>
The XML prolog itself must be UTF-8 encoded.
javadocdirectory of the JNLP Developer's Pack. (See the Developer's Section of the Java Web Start web site.)
Several sample applications that use the JNLP API are available on the Java Developer Connection website. Each includes a readme file that summarizes what is contained in the sample, source files for the application, and jar files with libraries and resources required to build, run, and deploy the application.
The samples are:
This is a simple word processing application that allows users to create, open, modify, save and print files. The WebPad application uses JNLP API extensively to access resources locally when running in the untrusted execution environment.
Random Access File Sample
This sample demonstrates features of the
JNLPRandomAccessFile interface of the JNLP API. The user picks up a file that is opened as a random file for both writing and reading.
Extension Installer Sample
This sample using the
ExtensionInstallerService feature of the JNLP API installs a native shared library to the client machine and informs the JNLP Client of a directory where it should search for native libraries.
Library (native) Installation
This sample uses the
<nativelib> element in the resources section of a JNLP file to install a native shared library on the client machine.
The purpose of this sample is to demostrate how CORBA applications can be deployed using Java Web Start. It includes a very simple "Hello World" application using RMI-IIOP.
Developers can access the Java Developer Connection SM Bug Parade database and vote for fixing those bugs that significantly affect their products and projects. The following is a complete list of all bugs that have been fixed in this release of the Java Web Start software that had at least one vote on Bug Parade. Each bug ID in the table is a link to the corresponding bug report on the Java Developer Connection web site.
|Bug ID||No. of votes||Synopsis|
|4393950||28 votes||request to allow codebase to be specified with an HTTPS location.|
|4474021||11 votes||JNLP version based protocol fails with war files|
|4476448||10 votes||There is a bug when finding updates on passworded servers|
|4510364||7 votes||Memoryleak in Java Web Start|
|4473369||4 votes||forceUpdate:true && jnlp:installer-desc == ENDLESS_LOOP|
|4502223||4 votes||Application Manager's shortcut icon is ugly|
|4393792||3 votes||Downloading new version of running app fails|
|4474870||3 votes||Windows installer won't recognize Java 1.3.1 fcs as usable jre.|
|4626716||2 votes||Autoinstall (Windows CAB-based internet component download) for JavaWS|
|4459387||2 votes||Unsigned application .... error for signed jar specified in component extension|
|4474861||2 votes||cached ico files are not purged or updated.|