Oxygen XML, JDL Security Manager

[Guilleradden]

Hello,

Beginning with JDK 17, Java SecurityManager is deprecated (https://bugs.openjdk.org/browse/JDK-8264713).
This displays the warning messages described in other threads.


Running SecurityManager-related code no longer works out of the box with Java 18+.
When using these latest Java versions, OygenXML's "independent distribution" (without bundled JRE) breaks on startup.
UnsupportedOperationException is thrown.
As a workaround, the additional JVM parameter -Djava.security.manager=allow should be specified.
It may be included in the start scripts (for example, oxygenDeveloper.sh).
I'm not sure if that will fix the problem in the future, but it still works with Oxygen 27 and OpenJDK 21.

Regards

[Radu]

Hi,

In general all our automated and manual tests are done with Oxygen with a certain Java VM version. So ideally you should avoid using the Oxygen all platforms distribution and use instead an installation kit which comes bundled with Java 17. Officially we do not support Java versions of flavors which have not been thoroughly tested with Oxygen.
Indeed with Java > 17 Oxygen can run only when its security manager is disabled, we have an internal issue to have it work even without disabling the security manager in the startup script. The security manager in Oxygen adds a certain security layer for certain operations, for example it shows confirmation dialogs when attempting to open remote URLs in Oxygen, so we need to work to have this mechanism implemented with other means.

Regards,
Radu