For the extension, are there plans to allow users to choose the JVM like the legacy apps do (setjavahome=xxx in product.conf)?
In Data Modeler legacy, I have a large relational model with several physical models. I wrote a transformation script with graalJS that uses UDP and templates to build/update the physical models. With graalJS running in interpretive mode with the standard Oracle Java 17, my (Windows 10) memory use gets high and the script take several minutes to run.
On another system, I installed the GraalVM for Java 17 as suggested by Jeff Smith (https://www.thatjeffsmith.com/archive/2024/10/oracle-sql-developer-data-modeler-24-3-are-now-available/)
The application and the transformation scripts seemed to run faster, but I didn't benchmark. It makes sense to me that using compilation mode with GraalVM would help with resource management at least, especially for the repetitive functions.
So while I understand the desire to make installation and initial product release as smooth as possible, I think it will be important to eventually allow better control of which Java we use. It would also help the issues where corporate users are blocked from running java.exe from their user folders.
And even though I know the answer will be “you'll have to wait and see” can you share ANYTHING about when and how Data Modeler will be implemented in the extension? Will it still support GraalJS?
Thank you!