-
Bug
-
Resolution: Duplicate
-
P4
-
9
-
None
When running with a SecurityManager, several permissions need to be granted to code that accesses the java.desktop module in the lib/security/default.policy file:
// permissions needed by applications using java.desktop module
grant {
permission java.lang.RuntimePermission "accessClassInPackage.com.sun.beans";
permission java.lang.RuntimePermission "accessClassInPackage.com.sun.beans.*";
permission java.lang.RuntimePermission "accessClassInPackage.com.sun.java.swing.plaf.*";
permission java.lang.RuntimePermission "accessClassInPackage.com.apple.*";
};
These permissions should not be necessary since the application is not accessing classes in these internal packages directly.
Information on which tests fail will be added as a comment to this issue.
// permissions needed by applications using java.desktop module
grant {
permission java.lang.RuntimePermission "accessClassInPackage.com.sun.beans";
permission java.lang.RuntimePermission "accessClassInPackage.com.sun.beans.*";
permission java.lang.RuntimePermission "accessClassInPackage.com.sun.java.swing.plaf.*";
permission java.lang.RuntimePermission "accessClassInPackage.com.apple.*";
};
These permissions should not be necessary since the application is not accessing classes in these internal packages directly.
Information on which tests fail will be added as a comment to this issue.
- duplicates
-
JDK-8173082 java/bean/* tests fail since change of JDK-8055206
-
- Closed
-
- relates to
-
JDK-8173082 java/bean/* tests fail since change of JDK-8055206
-
- Closed
-
-
JDK-8055206 Update SecurityManager::checkPackageAccess to restrict non-exported JDK packages by default
-
- Closed
-
-
JDK-8175558 TCK failure on MacOSX: The file can not be opened or saved
-
- Resolved
-
-
JDK-8175559 The file can not be saved
-
- Closed
-