NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Hi Luke:We always put the Java3D code in the JRE directory that we bundle with our applications (and development things like Python) - that way the users get the environment _we_ want them to have, not what they might have otherwise installed. We also make sure that they run our jvm. Why didn't they get an error before? Speculations:
* you had inadvertantly put the Java3D files in your JRE directory before packaging
* they already installed Java3D and were using itI would recommend that you package the Java3D plus anything else you need, right along with the app and the jvm.
tomp.s. Also, IMHO Java 1.4.1 should not be used. There were so many problems with it that it's just not worth the hassles. AFAIK the only really stable, working version has been 1.3.1 lately...although I've not thoroughly looked at 1.4.2 yet...
Luke.A.Catania@xxxxxxxxxxxxxxxxxxx wrote:
Is there a reason I did not get this error before? In a previous version of my application installer I did not bundle Java3D API with it, I just bundled the Java JRE, which was 1.2.2. Luke
-- Tom Whittaker (tomw@xxxxxxxxxxxxx) University of Wisconsin-Madison Space Science and Engineering Center Cooperative Institute for Meteorological Satellite Studies Phone/VoiceMail: 608.262.2759
visad
archives: