In VisAD, there are several "packages". For example, "visad.data.text" is a
package. In order for the classloader to find the contents of this package,
the CLASSPATH variable must point to the "root node". This is usually the
visad.jar file itself. (If you look at the files in the visad.jar file,
you'll file entries like: "visad/data/text/TextAdapter.class")
However, when you extracted the contents of the visad.jar file, the "root
node", like Bill said, is the directory that contains the visad subdirectory.
That's because the CLASSPATH says "look starting _here_". And when looking
for the package "visad.data.text", it will look "starting here" for a
Thus, if you were "in" the "/opt/visad-in-a-box" directory when you extracted
the contents of the visad.jar file, your CLASSPATH should only point to
Hope that helps clarify.
Victor Shum wrote:
Dear Visad users,
I just don't understand why even I have included the
classes in my classpath (in the setenv line which I
sourced), when doing the make compile there is still
complaints of its non-existence!
Thanks for your advice in advance!
package javax.media.j3d does not exist
Tom Whittaker (tomw@xxxxxxxxxxxxx)
University of Wisconsin-Madison
Space Science and Engineering Center
Cooperative Institute for Meteorological Satellite Studies