[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-2d-dev
Subject:    Re: RFR: 8273101: Eliminate the usage of threadgroup sandboxing in the java.util.logging
From:       Sergey Bylokhov <serb () openjdk ! java ! net>
Date:       2021-09-29 20:09:36
Message-ID: 0CGQo0Xsjz8WEKH4AonQJMAhYK3Bhc4wqrIQCSawfJk=.f414c9ed-bf36-4eae-bc37-372ccc8bcee1 () github ! com
[Download RAW message or body]

On Wed, 1 Sep 2021 06:31:16 GMT, Sergey Bylokhov <serb@openjdk.org> wrote:

> At the time Java supported applets and webstart, a special mechanism for launching \
> various applications in one JVM was used to reduce memory usage and each \
> application was isolated from each other. 
> This isolation was implemented via ThreadGroups where each application created its \
> own thread group and all data for the application was stored in the context of its \
> own group. 
> Some parts of the JDK used ThreadGroups directly, others used special classes like \
> sun.awt.AppContext. 
> Such sandboxing became useless since the plugin and webstart are no longer \
> supported and were removed in jdk11. 
> Note that this is just a first step for the overall cleanup, here is my plan:
> 1. Cleanup the usage of AppContext in the "java.util.logging.LogManager" class in \
> the java.base module. 2. Cleanup the usage of TheadGroup in the JavaSound
> 3. Cleanup the usage of TheadGroup in the JavaBeans
> 4. Cleanup the usage of AppContext in the Swing
> 5. Cleanup the usage of AppContext in the AWT
> 6. Delete the AppContext class.
> 
> The current PR is for the first step. So this is the request to delete the usage of \
> AppContext in the LogManager and related tests. 
> Tested by tier1/tier2/tier3 and jdk_desktop tests.

Does anybody have any other suggestions?

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

PR: https://git.openjdk.java.net/jdk/pull/5326


[prev in list] [next in list] [prev in thread] [next in thread]