The client and server software need Java 1.4.2 (or higher). The servlets require the Java Servlet library which is available from Java.com in the Java Enterprise Edition (J2EE), or via downloading a servlet engine such as Apache Tomcat.

In Java Web Start, dynamically-loaded classes (ie, plugins) run in a sandbox unless they are explicitly signed. Also, the protocol handler API prevents protocol handlers from being added if they are not loaded via the system class loader (i.e via the Java Web Start class loader). So the lack of plugin support and jeditresource protocol makes it useless.

It's an easy, robust, and secure way to deploy applications directly from the web. Developers can make applications readily available via the web. In addition, Java Web Start provides Java runtime environment (JRE) management capabilities, it's easy to set up, it's browser-independent, and it's an efficient way to deploy web application solutions. Users can easily access applications much as they would a web page--without a separate installation step.

NTLM support was added to Java 1.4.2 on Windows platforms only. You can use NTLM authentication with Java Web Start in 1.4.2 and beyond. The JAuthenticator dialog may contain some misleading text when using NTLM with Java Web Start 1.4.2, but this is fixed in Java Web Start 1.5.0.

HTTPS support was added to Java in version 1.4. You can use use HTTPS protocol for Java Web Start resources starting in version 1.2, but may encounter one of several problems that were addressed in Java Web Start 1.4.2. It is recommended to use at least Java Web Start 1.4.2 if using HTTPS protocol.

an example app that uses Java 3D together with Web Start check out Masa Takatsuka's JBeanStudio app . Check your JRE as Java 3D doesn't work with all JRE versions. When using JRE 1.3.0_02 (the JRE that is default for JBuilder 5) things won't work. You need at least JRE 1.3.0_03 on Windows. (JRE 1.3.0_03 comes with the full install of Web Start 1.0.1_01.)

Java™ Web Start is a technology of Sun Microsystems to deploy Java™ Desktop applications via the internet, without installing (platform dependent) binaries. See also the getting started section.

Everything you need to get started is in googleapi.jar. Advanced users may prefer to use their own Java SOAP implementations and use the WSDL file to generate client code.

Answer: Salsa was developed using the Java 1.4.1 compiler and virtual machine but the grammar is based on the Java 1.2 grammar. Some language features, such as assertions, will not parse with the salsa compiler. There is a noticeable difference between JDK 1.4 and earlier JDKs in terms of performance when using graphical debuggers and especially profilers for debugging Java programs in general.

We advise using Java SE 1.4.2 or higher. Java 1.3 should work mostly, but we do not advise using it. Always make sure you have the latest revision of the JVM of your choice. No. XINS requires a Java SE SDK during development and additionally a servlet container for deployment.

If your application is written to the Java 2 platform, and is delivered as a set of JAR files, there should be no need to revise your application. Make sure that your application retrieves all its resources (such as images and resource bundles) from a JAR file, since Java Web Start launches an application by invoking the public static void main(String[] args) method.

This form and many other features of the website take advantage of the extra features and power of the newer browsers to enhance and provide information to you. The JavaScript in these forms checks your information to make sure that you did not mistype. This will allow the most efficient processing of your information. It also allows the form to "remember" who you are so that you do not need to enter certain information again in the future.

Any client system that supports the Java version 1.2.2 or higher can use Java Web Start. Java Web Start works with virtually all browsers.

The underlying technology for Java Web Start, the Java Network Launching Protocol and API is being developed through the Java Community Process, so you can implement this protocol in any product. However additional licensing and terms must be met to implement any JCP technology including the JNLP technology.

Security is a key consideration of the Java Web Start design. In Java Web Start all applications are launched by default in a secure "sandbox."

The following was originally posted by mswanson as FYI: great debugging solution in Sun's Java Web Start and JNLP forum, for JDK 1.4: I would like to let the JWS community know of a great way to debug your JWS app. Solutions have been posted before but I haven't seen anything as easy as this: JDK}/bin/java -Xdebug -Xnoagent -Djava.

See the JNLP tutorial. Note that the current license somewhat restricts redistribution (see What is the licencing model? above). [edit]

This site is best viewed with Internet Explorer version 4.0 or greater, with JavaScript and cookies, style sheets, and frames enabled. Although we haven't tested them, later versions of Opera should work. Older browsers and WebTV may be used to view the site, but expect some functionality and/or formatting to be lost.