JDK-8342992 : Security manager check should not use deprecated methods
  • Type: Bug
  • Component: javafx
  • Sub-Component: other
  • Affected Version: jfx24
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2024-10-24
  • Updated: 2024-11-16
  • Resolved: 2024-11-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
jfx24 b17Fixed
Related Reports
Blocks :  
JDK-8341090 - Remove support for security manager from JavaFX
Blocks :  
JDK-8342997 - Remove use of System::getSecurityManager and SecurityManager from JavaFX
Description
The <clinit> methods of PlatformImpl and LauncherImpl check whether security manager is present and throw UnsupportedOperationException if it is. This check currently uses the deprecated System::getSecurityManager and should be rewritten to use reflection so that we aren't calling API that is deprecated for removal. Additionally, ensure that this check is done from all places where it is reasonably needed. In addition to the two current places, we should consider adding it to FXMLLoader in the javafx.fxml module, and ReflectUtil and MethodUtil in javafx.base. To avoid code duplication, create a utility method in javafx.base that does this check.
Comments
Changeset: 5ac5009d Branch: master Author: Kevin Rushforth <kcr@openjdk.org> Date: 2024-11-08 16:58:25 +0000 URL: https://git.openjdk.org/jfx/commit/5ac5009deed0e9c72683a936b26a5c8b081ac58e
08-11-2024
A pull request was submitted for review. Branch: master URL: https://git.openjdk.org/jfx/pull/1627 Date: 2024-11-05 19:37:05 +0000
05-11-2024