javaws has inconsistent behaviors depending on whether an
application is started from the Application Cache Viewer
or by providing a URL on the command line. Specifically,
these two different invocation scenarios result in two
different JREs being used.

$HOME/.java/deployment/deployment.properties contains the
following:

#deployment.properties
#Fri Apr 28 19:00:21 PDT 2006
deployment.javaws.splash.index=/home/tomiii/.java/deployment/cache/javaws/splash/splash.xml
deployment.version=1.5.0
deployment.console.startup.mode=SHOW
deployment.javaws.viewer.bounds=1485,17,692,516
deployment.browser.path=/usr/sfw/bin/mozilla
#Java Web Start jre's
#Fri Apr 28 19:00:21 PDT 2006
deployment.javaws.jre.0.enabled=true
deployment.javaws.jre.0.location=http\://java.sun.com/products/autodl/j2se
deployment.javaws.jre.0.osarch=sparc
deployment.javaws.jre.0.osname=SunOS
deployment.javaws.jre.0.path=/usr/dist/share/java,v1.4.2/5.x-sun4/bin/java
deployment.javaws.jre.0.platform=1.4
deployment.javaws.jre.0.product=1.4.2
deployment.javaws.jre.0.registered=false
deployment.javaws.jre.1.enabled=false
deployment.javaws.jre.1.location=http\://java.sun.com/products/autodl/j2se
deployment.javaws.jre.1.osarch=sparc
deployment.javaws.jre.1.osname=SunOS
deployment.javaws.jre.1.path=/usr/jdk/instances/jdk1.5.0/jre/bin/java
deployment.javaws.jre.1.platform=1.5
deployment.javaws.jre.1.product=1.5.0_06
deployment.javaws.jre.1.registered=true
#Java Plugin jre's
#Fri Apr 28 19:00:21 PDT 2006
deployment.javapi.jre.1.5.0_06.osname=SunOS
deployment.javapi.jre.1.5.0_06.args=
deployment.javapi.jre.1.5.0_06.osarch=sparc
deployment.javapi.jre.1.5.0_06.path=/usr/jdk/instances/jdk1.5.0/jre


If I attempt to start Sun's Instant Messenger application
via the command line, I get JRE 1.5.0:

    javaws http://im.sun.net/en/imssl.jnlp

However, if just type "javaws" and then launch IM from the
Application Cache Viewer, I get JRE 1.4.2. Since IM does
not currently work properly with 1.5.0 (or perhaps just my
specific build, 1.5.0__06), I always want IM to use 1.4.2.
Why do I see this inconsistent behavior depending on how
I launch the application?