Posted by gmrolf on Aug 27, 2012; 3:41pm
URL: https://forum.jogamp.org/how-to-run-jogl-j3d-successfully-tp4025876p4025907.html

gouessej wrote

I'm sorry, I used them during Siggraph with another machine, I don't have these JARs anymore, you will have to rebuild Java 3D yourself or contact Harvey on Github.

I gave a try on waiting for harvey...loads of other works are here which have to do... the rebuilding could be a solution but I have to remind how to do that...long time ago... on the other hand I believe will be nice if your tutorial links point to the correct jars...so waiting for Harvey would be the best solution I believe. he told me that he'll have a look inside here one ore the other day...if not I try to reproduce how to build it...

gouessej wrote

lib/ext folder is the directory reserved for official extensions, they are treated as system libraries, it is not a trivial difference in term of security. When you use any Java application, Java tries to use them first. If any Java application or applets needs to use another version of a third party that should have never been put into this directory, it will use the version in lib/ext instead of the one in the classpath. Putting everything into lib/ext defeats the purpose of the classpath. "Optional packages" or "standard extensions" should be used only for frozen APIs. Some softwares use none of these mechanisms to retrieve classes, they build their own system class loader with their own path, for example Apache Tomcat does so.

OK, sounds logical! as I am more a some-times-programmer I'd never stumbeld over that. When developing any tools I try to put any needed 3rd party jars directly in the folder of the Source, so it is save that only that version will be token. If the "." is in the classpath (...) The other Point  I'd (may) never realized - but good to know and would be integrated in my future.

gouessej wrote

Just look at StackOverflow, some people already gave similar answers. Using the classpath is not difficult and I have wasted a lot of time with students and engineers with messy environments when using JOGL and Java3D. The problem is that even some commercial softwares wraps some existing APIs and put them into this directory...

If you're really convinced I'm totally wrong, just put JOGL 1.1.1a JARs into lib/ext and try to run an applet using JOGL 2.0...

using of classpath isn't a magic thats true - wasting time is not a good thing - so you won 2:0  
thanks for explanation!
best wishes
rolf