![]() ![]() Using Update 65 or later, or Oracle JDK 8 using Update 20 or later. It would be much clearer if the wording was: Do not interpret later as implying that Glassfish 4.1 might work with Java 9 or higher. The word later in the part stating Oracle JDK 8 Update 20 or later is ambiguous, but it is referring only to the update level for the specified JDK version. Update 65 or later, or Oracle JDK 8 Update 20 or later. GlassFish Server Open Source Edition Release 4.1 requires Oracle JDK 7 The Release Note will have a section titled Hardware and Software Requirements, and within that a sub-section titled Required JDK Versions. The best (and easiest) approach for determining whether Java version x will work Glassfish version y is to refer to the Release Note for that specific Glassfish release. console.log – Will it be possible to use Java 8 on Glassfish 4.1? That can of course change the runtime characteristics of large applications running in a large stack. A new jvm may use different defaults for say, garbage collection settings (or use a different gc in the first place). Of course, there can be subtle issues for large applications. But at least for now, the corresponding checking can be disabled on the command line. And for the record: Java 9 (or newer) with the new module system is a completely different story. So, the (unspecific) answer here is: just try it. The other way round (upgrading your application server for example) is much more likely to cause significant problems. And most importantly: a new jvm can always run byte code compiled for an older version of Java. Keep in mind that a lot of work goes into making sure that new Java versions are backwards compatible. In general: updating the jvm version alone rarely leads to issues. Console.log – Will it be possible to use Java 8 on Glassfish 4.1?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |