On Thu, 11 Jun 2026 13:49:33 GMT, Jaikiran Pai <[email protected]> wrote:
> Can I please get a review of this change which moves the `jdk.naming.rmi` > module to be loaded by the platform loader, instead of the boot loader? > > This module doesn't require any extra priveleges and as such isn't needed to > be part of the boot loader. This module provides the > `javax.naming.spi.InitialContextFactory` service. Before this change, the > service would be located and loaded using the boot classloader and now will > instead be loaded using the platform classloader. I believe this change to > the service loading is an observable change and would thus require a CSR. > I'll create one shortly. > > A new jtreg test has been introduced to verify that the > `InitialContextFactory` service provided by the `jdk.naming.rmi` module > doesn't get loaded by the boot loader. The test passes with this change and > fails (as expected) without the source change. > > --------- > - [x] I confirm that I make this contribution in accordance with the [OpenJDK > Interim AI Policy](https://openjdk.org/legal/ai). The title of the issue could be changed, as deprivileging means granting fewer permissions which no longer applies since the Security Manager is permanently disabled. Maybe change to "Move jdk.naming.rmi module to platform class loader" ------------- PR Comment: https://git.openjdk.org/jdk/pull/31480#issuecomment-4681525249
