- As this patch includes a major JRE upgrade (JRE v17), it is recommended that you apply this patch to a test environment before applying it to production.
The upgrade to Java 17 upgrade may require you to handle the conflicts that may occur with custom jars or custom classes. You may come across the following scenarios wherein you need to take the necessary actions to address the conflicts. Java packages used in the custom plugin, custom jars, or custom classes may have changed. To address this issue, you need to change the custom plugin, custom jars, and the custom classes accordingly. Classes used in custom plugin, custom jars, or custom classes may have been deprecated or their implementation may have changed. To address this issue, you need to change the custom plugin, custom jars, and the custom classes accordingly. Although Java 17 is backward compatible – code compiled with Java 8 continues to run on Java 17 most of the time – there are certain restrictions implemented in Java 17, for example, Java 17 restricts the use of certain packages and reflections. However, you can override these restrictions by adding the required entries in the launcher.properties file. External jar(s) in the ext folder may not be compatible with the upgraded versions of the framework. In this case, jars need to be upgraded accordingly.
|
