Java.lang.NoClassDefFoundError: com/sun/j3d/utils/applet/MainFrame at HelloUniverse.main(Compiled Code)

Question

I'm getting this error
java.lang.NoClassDefFoundError: com/sun/j3d/utils/applet/MainFrame
at HelloUniverse.main(Compiled Code)
I receive this error when I try to run the demos that are in the /usr/java1.1/demo folder.
I followed the directions to install java3d. I installed the java3d binary in the top part of
the JDK directory then ran the binary. Everything installed o.k., but I cannot run
any of the demos. I also have J2SE 1.2.2_05a, JDK 1.1.8_10, and.
JRE 1.1.8_10 installed. My operating system is SunOS 5.6, Solaris 2.6. My workstation
is an Ultra 5 with 374mb ram.
Here is part of the install intructions.
Place the java3d1_2-solsparc.bin file into the top level directory
of the JDK you wish to install Java 3D into. Execute the
java3d1_2-solsparc.bin file (ex: sh java3d1_2-solsparc.bin).
After installation, you may remove this file.
The Java 3D(TM) SDK includes several demo programs that can
verify correct installation. Assuming your Java 2 SDK is installed
at ~/Solaris_JDK_1.2.2_05, try the following:
cd ~/Solaris_JDK_1.2.2_05/demo/java3d/HelloUniverse
java HelloUniverse
Note: Many more demos are available under the demo/java3d/
directory. Some of the demos require a maximum memory
pool larger than the default in java. To increase the
maximum memory pool to 64 meg, add the following command
line options to java or appletviewer:
java: -mx64m
appletviewer: -J-mx64m
You do not need to include the J3D jar files in your CLASSPATH,
nor do you need to include the J3D shared libraries in your PATH.
You should include "." in your CLASSPATH or ensure that CLASSPATH
is not set.
I'm not sure how to set set/unset the CLASSPATH and I'm not sure if I was supposed to
place the binary file in the /usr/java1.1 or /usr/java or /usr/java1.2 directory.
Can anyone help?
tomjones

Answer 1

-- If jar size isn't an issue, I recommend using thick "weblogic.jar" instead of the thin "wl*.jar" jars. The thick jar is a better performer, is used by more customers, and has more features. Otherwise:
          -- It might help to use the thin client jars from a later service pack - several service packs have been released since SP2, or you might even try using jars from a recent 9.2 SP or even 10.0.
          -- Also, check to see if the 1.4.2 JVM is up-to-date and/or try switching from the Sun JVM to the JRockit JVM (or vice-versa).
          -- Finally, it might help to check if your XP environment matches your Linux environment (JVM command-line, classpath, etc).
          -- Also: The IIOP newsgroup may also have some advice. The thin client uses the IIOP protocol even when a "t3:" URL is specified by the application.
          Tom