On Thu, 23 May 2024 13:28:16 GMT, Chen Liang <li...@openjdk.org> wrote:
> I have updated the compatibility risk description of the CSR. > > My CSR proposes to allow dynamic unloading of the proxy implementation > classes, but currently it's not implemented as they are strongly referenced > in the ClassLoaderValue caches. Should I implement dynamic unloading > suggested in the CSR in this patch, or should I do it later? I think the main compatibility concern is going to be that hidden classes don't have a binary name so we have to get a sense as to whether there are frameworks that do anything with the class name and Class.forName. I suspect the work will also mean looking at cases where agents are somehow instrumenting proxy class (hidden classes are not modifiable). In the JDK 8 time frame we had to back out a change in this area due to one of the mocking tools filtering by class name and trying to redefine proxy classes. ------------- PR Comment: https://git.openjdk.org/jdk/pull/19356#issuecomment-2127188839
