Posted by
Sven Gothel on
Dec 19, 2011; 9:40pm
URL: https://forum.jogamp.org/Trying-to-upgrade-to-JOGL-2-0-tp3599602p3599661.html
On Monday, December 19, 2011 10:15:27 PM Tomd [via jogamp] wrote:
>
> I've been using JOGL 1.1.1 forever, and I have finally decided to upgrade to
> 2.0. I am using b23, is that best?
You mean RC5 ? Yes, sure.
>
> Anyway, I've messed around for most of the afternoon trying to get it to
> work with a really simple test app. I am pretty sure I am loading the b23
> jars, and using the b23 DLLs (because it behaves differently if I change
> either of those). I have one final error:
>
> Exception in thread "main" java.lang.NoClassDefFoundError:
> javax/media/nativewindow/WindowClosingProtocol
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
> at
> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
> at java.net.URLClassLoader.access$000(URLClassLoader.java:56)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
Looks like you are not using jogl.all.jar, but the atomic ones ?
For the latter you need to include the nativewindow JARs as well,
however, I would encourage the jogl.all.jar's ..
Wade likes to update our Wiki page .. however, here is a little overview
about the new JAR files, etc:
http://forum.jogamp.org/setting-up-JOGL-in-Eclipse-on-Mac-OSX-Lion-Frustration-td3435692.html#a3436274http://forum.jogamp.org/JogAmp-Deployment-Enhancements-Automatic-loading-of-native-JARs-Applet-Application-td3362447.html>
> Does this mean I am missing a DLL or a JAR? Any idea which one?
Just a missing JAR .. yup.
>
> Sorry I know this sort of question comes up a lot, but I've been on this for
> hours and I'm running out of things to try.
NP.
IF in doubt, check the
http://jogamp.org/deployment/jogamp-current/jogl-test-applets.htmlpage and see what we are loading (JARs) to run some demos.
Or .. 'simply' check our junit tests.
~Sven