I hope for providing support for Open Source Java for Creo Elements Direct Model Manager. I think it's possible to reduce customer's burden and to make easy to upgrade by offering to provide support for Open Source Java.
"not using Java" would mean that Model Manager would Need to be rewritten from scratch. So this is definitely out of scope. The time we (including me) developed Model Manager, JAVA was free and nobody had an idea that Oracle will buy SUN including Java. Model Manager customers are only a few of Millions of other customers that are affected by the changed Java policy.
I hope for providing support for Open Source Java for Creo Elements Direct Model Manager. I think it's possible to reduce customer's burden and to make easy to upgrade by offering to provide support for Open Source Java.
Good news - indeed! The changed JAVA support policy of ORACLE was a major road blocker for upgrading Model Manager. Now all customers can move on to using the latest version of the Software 🙂
btw. We were using open JDK versions even with Model Manager before 20.3 - just for testing "if it works". But this was mothing we would ever recommend for a productive Environment.
Additional Hints concerning Coretto: - Be careful with Coretto Updates
- Model Manager Clients *and* the installation on the Server remember the path to the Coretto Installation
- So you MUST NOT change the path of the Coretto Installation - but this exactly happens if you install a newer version of Coretto using the MSI installer
The root of this problem is that the PTC products no longer ship *with* a JAVA JRE/JDK as this was the case in earlier versions.
Instead of the MSI we are downloading and unpacking the ZIP archives. This way it is possible update Corretto "in place" to avoid issues with applications which remember the path to the Corretto (JAVA) installation. (useful for Model Manager and Windchill).
