> Michael> Netscape does equally complex stuff. It tries to find
> Michael> itself (and there is a setting but I forgot what it was)
> Michael> and once it does, it does even more by automatically
> Michael> adding *all* jar files in the directory where it stores
> Michael> its jar files. This is so that plug-in and add-on java
> Michael> things can be done without the CLASSPATH setting. Note
> Michael> that there actually is a problem with some versions of
> Michael> Netscape where if you have CLASSPATH defined at all when
> Michael> Netscape runs it does not try to find its own Java
> Michael> directories and thus will fail to run Java. The best
> Michael> thing to do is not to have CLASSPATH defined when
> Michael> starting Netscape.
>
> export MOZILLA_HOME=/path/to/top/of/netscape/directory/tree
>
> Navigator will then successfully find the jar files it needs.
>From netscape README file:
Java Applet Support:
Java Applet support is available for all Unix platforms.
To run Java applets with the Java-enabled version, Communicator
needs to be able to load Java class files from a file called
java40.jar. This file is included in the distribution, and is
searched for using the following algorithm:
if($CLASSPATH environment variable is set)
Look at $CLASSPATH, where $CLASSPATH is a
colon-delimited list of <path>/<jar-file> entries.
else
Search in order:
<program directory>
$MOZILLA_HOME/java/classes
$HOME/.netscape
/usr/local/netscape/java/classes
/usr/local/lib/netscape
--
Cheers.
Alexander
