Java 3d versions and JDK compatibility

[sstevenson638]

This issue is to message @philjord with a question. There appears to be two diverging versions of java3d, version 1.7 under the Philjord path, and version 1.6 under the hharrison path. Which one should I use? Based on browsing the repositories it appears like 1.7 is a little more up to date.

I have a legacy application using java3d 1.5 and java 8. We want to update to a newer version of java and are looking to upgrade to a newer version of java3d also. I would like to move all the way to java 25. However, based on the source code, java3d 1.7 may be limited to java 17. The java security manager was dropped in java 24 and I saw usages of it in java3d 1.7. Can you verify this? If I wanted to contribute would it be hard for me to remove usages of security manager from java3d 1.7? Are there other potential blockers to using java3d in java 25?

Thank you

[philjord]

Hi sstevenson638,
Version 1.6 under hharrison is the older version, and 1.7 under philjord is the continuation.

1.6.2 is the latest release of 1.6
1.7.1 is the stable release of 1.7
1.7.2 is the working head of 1.7, not yet released

Between the two the largest difference, and a barrier for many to update is the package name. The javax package was a core package for java and not appropriate for a community project to be within, so the base package of javax.media.j3d was been modified in all case to be org.jogamp.java3d

This package is used as java3d was picked up by the jogl organisation after it's abandonment by sun many decades ago. (I see now that I've looked at the jogl home page it is not updated to point at version 1.7)

You are correct that Java3D is not tested with Java 25, and has only been tested thoroughly up to Java 11.

The SecurityManager use seems vestigial now, though to be safe it would be best to change teh 3 occurances like so

SecurityManager sm = System.getSecurityManager();
	boolean doExit = true;
	if (sm != null) {
	    try {
		sm.checkExit(0);
	    } catch (SecurityException e) {
		doExit = false;
	    }
	}

	final boolean _doExit = doExit;

        // WindowListener inner class to detect close events.
	addWindowListener(new WindowAdapter()
        {
            @Override
            public void windowClosing(WindowEvent winEvent)
            {
		<snip>

		if (_doExit) {
		    System.exit(0);
		}

            }
        });

to

  // WindowListener inner class to detect close events.
	addWindowListener(new WindowAdapter()
        {
            @Override
            public void windowClosing(WindowEvent winEvent)
            {
		<snip>

		try {
		    System.exit(0);
		} catch (SecurityException e) {}
            }
        });

If you did this under 1.7.1 and added a pull request I can accept it into the 1.7.2 version without conflict.

Thanks,
Phil