Posted by
Sven Gothel on
Feb 28, 2012; 12:19am
URL: https://forum.jogamp.org/JOGL2-RC5-on-Windows-Vista-has-a-NoSuchMethodError-on-javax-media-opengl-GLDrawableFactory-initSingl-tp3782200p3782563.html
On 02/27/2012 10:43 PM, Martin [via jogamp] wrote:
>
>
> Hi,
>
> A jzy3d user has a problem initializing a GLCapabilities. A very simple code
> without jzy3d can let jogl fail:
>
> public class StupidTest {
> public static void main(String[] args) {
> new GLCapabilities(GLProfile.getDefault());
> }
> }
>
> Will:
> Exception in thread "main" java.lang.NoSuchMethodError:
> javax.media.opengl.GLDrawableFactory.initSingleton()V
> at
> javax.media.opengl.GLProfile.initProfilesForDefaultDevices(GLProfile.java:1244)
> at javax.media.opengl.GLProfile.access$000(GLProfile.java:75)
> at javax.media.opengl.GLProfile$1.run(GLProfile.java:133)
> at java.security.AccessController.doPrivileged(Native Method)
<snip/>
>
> Some info on the computer:
> OS: windows vista home edition, service pack 2
> GC: SiS Mirage 3
> Proc: Intel pentium dual CPU T3400
>
>
> The list of jars in the path:
> gluegen-rt-natives-linux-amd64.jar
> gluegen-rt-natives-linux-i586.jar
> gluegen-rt-natives-macosx-universal.jar
> gluegen-rt-natives-solaris-amd64.jar
> gluegen-rt-natives-solaris-i586.jar
> gluegen-rt-natives-windows-amd64.jar
> gluegen-rt-natives-windows-i586.jar
> gluegen-rt.jar
> jogl-all-natives-linux-amd64.jar
> jogl-all-natives-linux-i586.jar
> jogl-all-natives-macosx-universal.jar
> jogl-all-natives-solaris-amd64.jar
> jogl-all-natives-solaris-i586.jar
> jogl-all-natives-windows-amd64.jar
> jogl-all-natives-windows-i586.jar
> jogl.all.jar
>
>
> I don't have this problem on my Win7.
>
> Hope you have some suggestions.
> Thanks for her,
If this would be a problem within JOGL, no unit test would pass.
Also, you would not be able to run lets say an Applet from the web page.
What could be the problem is that somehow JARs got mixed up.
However this doesn't sound logical since both classes GLProfile and
GLDrawableFactory are in jogl.all.jar.
Now I start tapping in the dark:
- some weirdo anti-virus software or other background thingy
manipulating the JARs ?
- check JAR files itself .. cmp them w/ the ones from our website
md5/sha256/cmp ..
- ??
Actually all platforms are using the same jogl.all.jar,
which contains the classes which seem to be incomaptible
in your case .. so, it's really 'interesting'.
> Martin
~Sven