The Web Start sandbox for unsigned apps doesn't include the permission: awt.showWindowWithoutWarning. Thus, unsigned/untrused apps running in the sandbox show a banner (on top on Unix, on bottom on Windows) on all top level windows. Signed applications with all-permissions will not show it. If you want the Unix warning moved to the bottom like on Windows cast your vote for Bug #4673898.

MIMIC is a client/server application, i.e., it consists of two complementary sets of programs. The server program mimicd needs to run before the client programs mimicview and mimicsh can do their work. When you start mimicview, the GUI client, it starts the server program mimicd automatically, if it is not already running. If so, it also starts a logging window to dump the diagnostic output of the server program. If mimicd is already running, mimicview just attaches to it.

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.

Sun Microsystems provides versions for Windows 98/NT/2000/XP/2003, Solaris Operating Environment (SPARC and Intel editions) and Linux/i486. Apple provides a version for their OS X release.

When a user clicks on a Java Web Start link, a file called a JNLP file is downloaded and then read by the Java Web Start helper application. The JNLP file is a small XML document that contains information about the application that the user is trying to launch, where the application is located on the network, the application version, and the version of the Java Runtime Environment (JRE) that is required to run the application.

The presence of this orange DDD logo indicates that TriDef Visualizer has successfully enhanced this application and you should be experiencing a 3D effect. If not, please check the 3D settings (3D Scene Depth, Percent Behind Screen) for this application in the TriDef Control Panel.

The two approaches are very similar. The key difference is in the user experience. If the Java application/applet needs to interact with a web page and be tightly bound to a web browser, then applets may be the solution. On the other hand, if browser independence is important, then Java Web Start is the deployment platform of choice. There are a number of other differences, but this is the fundamental difference.

Note: The following applies to specific versions of Java, notably the 1.4 series. With Java 1.5.0 beta 1, the warnings are different, and thankfully less scary. I'll mention first that the most powerful way to use Frink is still the one outlined in Downloading Frink, which is what I'd recommend to power users and programmers. Java Web Start works okay if you only want to use Frink as a calculating tool, and not to write programs.

On Windows, Web Start is installed silently during the installation of the Java 1.4. Look for a Web Start icon on your desktop. There will also be an entry for Web Start in the Start --> Programs menu. On Solaris and Linux, the installation script for Web Start is contained within a zip file that you can find in the jre directory of the JDK (or in the top level of the JRE). Move the zip file to a location where you would like to install Web Start.

Java Web Start provides a platform-independent, secure, and robust deployment technology. It enables developers to deploy full-featured applications to end-users by making the applications available on a standard web server. With any web browser, end-users can launch the applications and be confident they always have the most-recent version.

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]

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.