RFR: 8344066: Remove SecurityManager uses from the jdk.accessibility module

[Phil Race]

On Wed, 20 Nov 2024 05:13:29 GMT, Abhishek Kumar <abhiscxk at openjdk.org> wrote:

> Since JEP 486 : Permanently Disable the Security Manager [JDK-8338625](https://bugs.openjdk.org/browse/JDK-8338625)
> is now integrated, calls to java.security.AccessController.doPrivileged  and SecurityManager.checkPermission are obsolete and can be removed.
> 
> This PR takes care of the files in the jdk.accessibility module.
> 
> Tested swingset2 application with JAWS to verify a11y functionality on component. CI testing looks ok.

What about the 52 (?) uses of SecurityException in these files ?
eg
AWTEventMonitor.java:                } catch (SecurityException e) {
SwingEventMonitor.java:                } catch (SecurityException e) {

The question is, what code would throw that exception ? 
If it is not possible any more, these are no longer needed.
If it IS possible, then they are still needed.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/22267#issuecomment-2489815248