https://bugs.documentfoundation.org/show_bug.cgi?id=97827
--- Comment #12 from Buovjaga <ilmari.lauhakan...@libreoffice.org> --- Some more facts from Michael: https://lists.freedesktop.org/archives/libreoffice/2022-January/088381.html Quote: another problem is that Rhino cannot simply be replaced by packging yet another JS implementation; if you look at the examples we ship, they have: importClass(java.lang.Thread); importClass(java.lang.System); so any existing Rhino based macros will likely use the Java APIs and cannot work with a non-JVM based JS implementation. importClass(Packages.com.sun.star.uno.UnoRuntime); importClass(Packages.com.sun.star.lang.XMultiComponentFactory); importClass(Packages.com.sun.star.awt.XDialogProvider); importClass(Packages.com.sun.star.awt.XDialog); importClass(Packages.com.sun.star.uno.Exception); importClass(Packages.com.sun.star.script.provider.XScriptContext); also, Rhino relies on the Java-UNO bridge and some Java glue code in the scripting module to provide access to UNO APIs; this would need to be reimplemented in the form of a bridge for any non-JVM based JS implementation. -- You are receiving this mail because: You are the assignee for the bug.
