Name: acR10002 Date: 11/19/2000


Since b12 build JaWS installation script for Solaris (i.e. javaws-1_0-*-bin-*-solsparc-*.sh)
no longer creates a link from users .javaws directory to master javaws.cfg file (i.e. no
longer does ln -s ${INSTALLDIR}/javaws.cfg ${HOME}/.javaws/javaws.cfg). Now ~/.javaws/javaws.cfg
is created after first time javaws application manager is invoked (from the installation directory).
However, the javaws.cfg file created doesn't contain any path to JRE. Later, if one executes
javaws from a different location (i.e. not from installation directory, but from, for example,
/re/promoted/javaws), then it fails with a message:

Java(TM) Web Start 1.0-beta Error, process exiting...
Bad installation. No JRE found in configuration file: No such file or directory

because ~/.javaws/javaws.cfg doesn't contain any JRE path.
This behavior is strange and confusing. If one has decided ~/.javaws/javaws.cfg will no
longer be used, this file shouldn't be created at all and user is not allowed to execute
javaws from a location different than installation directory. But if user is still allowed
to do it, ~/.javaws/javaws.cfg should be created with valid contents, i.e. should at least
contain all necessary paths to JRE.

======================================================================