Posted by
Xerxes Rånby on
Dec 16, 2013; 3:07pm
URL: https://forum.jogamp.org/java3d-memory-leak-with-threads-tp4030899p4030917.html
2013-12-16 15:58, henry [via jogamp] skrev:
> HI Julien and August,
> I'm sorry - I did not mean to offend anybody.
> I''m just C/C++ programmer who has stepped out of comfort zone and got bitten.
>
> I've checked the version of java3d i am using and it is v 1.5 . So what you are saying is that your 1.6 version is not backwardly compatible and if I want to use v1.6 then I'll have to recode
>
> McIDAS is a large programs and on start up loads over 10,000 classes - most of it is open source
> It is maintained by the Space Science and Engineering Center at the University of wisconsin
>
> I would just like some idea of the scale of the task before I start !
> Is it just a mater of changing a few method calls or is there a paradigm shift ?
>
> Many thanks
> ... Henry
>
You only need to add the new Java3D 1.6 jar(s)
j3dcore.jar
j3dutils.jar
vecmath.jar
and the jogamp jar(s)
jogl-all.jar
jogl-all-natives-linux-amd64.jar
jogl-all-natives-linux-i586.jar
jogl-all-natives-macosx-universal.jar
jogl-all-natives-windows-amd64.jar
jogl-all-natives-windows-i586.jar
joal.jar
joal-natives-linux-amd64.jar
joal-natives-linux-i586.jar
joal-natives-macosx-universal.jar
joal-natives-windows-amd64.jar
joal-natives-windows-i586.jar
gluegen-rt.jar
gluegen-rt-natives-linux-amd64.jar
gluegen-rt-natives-linux-i586.jar
gluegen-rt-natives-macosx-universal.jar
gluegen-rt-natives-windows-amd64.jar
gluegen-rt-natives-windows-i586.jar
to your classpath, the Java3D API is identical and your application should work without any code change.
http://gouessej.wordpress.com/2012/08/01/java-3d-est-de-retour-java-3d-is-back/#installationDeployment will be easier because you can bundle all Java3D 1.6 and JogAmp jars with your application.
You no longer need to install java3d manually on the clients.
We recommend that you un-install the old java3d 1.5 version from the clients.
Cheers
Xerxes