Giuseppe,
I don't use VisualAge so I'm guessing here.
If your application compiled then VisualAge was able to find all the JAR
files it needed. If you could not *run* your application then I'd guess that
the runtime DLLs could not be located to execute the native graphics calls.
I'd make sure the DLLs are in the path somehow, either through a VisualAge
setting or an OS setting.
Hope that helps a little,
Daniel Selman
[EMAIL PROTECTED]
http://www.tornadolabs.com
-----Original Message-----
From: Discussion list for Java 3D API
[mailto:[EMAIL PROTECTED]]On Behalf Of Giuseppe Annunziata
Sent: 14 December 1999 05:09
To: [EMAIL PROTECTED]
Subject: [JAVA3D] Java3D with VisualAge Java
Hello,
I tried to compile and running under VisualAge a Java3D example:
SimpleUniverse.java.
Since VisualAge haven't a native Java3D support, I made an import of all
Java3D *.jar as well (VisualAge mades an deep analizing of this .jar).
In compiling time VisualAge internal compiler has no problem.
Early make a run, has a problem, an exception on the constructor call:
java.lang.unsatisfiedLinkException <class java.library.path do not contain
J3D>
or similiar.
This can be caught by the IBM VisualAge JVM 1.2.0 that isn't updated to
1.2.2, but I'm not sure.
Anybody can help me?
thanks in advance.
--
Annunziata Giuseppe [EMAIL PROTECTED]
CRMPA developer H2oT Interative
Computer Science Student at Universita' degli Studi di Salerno
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
