Hello,
I expect this information is to be found in some posting on this forum, but my search queries didn’t yield it.
As I understand it, JOGL (under the name JSR-231) is slated to be included into the standard Java SE distribution in the near future. Is that still the case? Has a a more specific date or release-version been made public?
Thanks in advance for any information,
Charles Gunn
As the JOGL project lead I have been resisting putting JSR-231 into the core Java SE distribution. Java SE has become a large monolithic system and continuing to put more into it only exacerbates the problem. JOGL can be effectively distributed to end users as a standard extension in both Java Web Start applications and applets with no manual installation, so I don’t see a strong reason to bundle it into the core APIs. What do you think?
additionally to that, if the consumer Runtime is out next spring, it wont be anymore relevant what is inside the standard Java SE and what not. It will be downloaded/installed on demand to the module system.
Even now we have projects evolving much faster than the JDK (eg. JAXB) which leads into lib redundancy (if you need the newest version for your project). The same applies for JOGL (we need a new build if OpenGL evolves).
so these problems hopefully should be all solved if the consumer RE is available (and the module system is usable…).
Ken,
Thanks for the information. I’m content with the situation as it is. The motivation for the original post was an inquiry by a possible user of our software (www.jreality.de), who was concerned that JOGL somehow might be less “official” than Java3D. What is the status of Java3D in this respect? Is it also a JSR project? Is it slated to be included in the standard release? (I did read the post regarding the possibility that JOGL might become the default OpenGL backend for Java3D, so obviously the two packages are not considered competitors (nor in my opinion should they be)).
If it’s not going too far, it would also interest me to know what is the significance of the “JSR” process; my impression was that, when successful, it led to inclusion in the standard release. Your reply implied that JSR validation means that the Java community officially recognizes JSR-231 as a “standard extension”. Is there a more specific definition of what that term means?
bienator – thanks also for your post. Unfortunately I don’t know anything about the Consumer Runtime Environment. It sounds like the core runtime would be actually reduced and many packages would become like JOGL, to be loaded on demand. Could you point me to a URL where I might find out more?
no problem.
here a nice description of the Consumer JRE:
http://weblogs.java.net/blog/chet/archive/2007/05/consumer_jre_le.html
and here (more technical) about the module system
http://weblogs.java.net/blog/stanleyh/archive/2007/06/openjdk_modules.html
Java 3D is another standard extension developed under the Java Community Process. Java 3D and JOGL are equally “official” by whatever definition of the word you like.
My perception of the process, from going through it with JOGL, is that it’s more of an industry vetting of a certain set of APIs to make sure that when a certain portion of the API namespace is carved out that the result is solid. JOGL certainly evolved substantially during the JSR-231 development process.