RFR: 8331467: FileSystems.getDefault fails with ClassNotFoundException if custom default provider is in run-time image [v9]
liyazzi
duke at openjdk.org
Thu Dec 19 12:38:27 UTC 2024
> For two cases:
>
> 1. When the ImageReaderFactory was loaded by local jdk,that means the ImageReaderFactory was loaded by boot class loader,then init the `Path BOOT_MODULES_JIMAGE` by using `sun.nio.fs.DefaultFileSystemProvider` which is obtained through reflection,due to it is in jdk internal.
> 2. When loaded by a target jdk, such as jdk8 runtime, then use the Java 8 compatible APIs: `FileSystems.getDefault()` to init the `BOOT_MODULES_JIMAGE` field.
> Then we can avoid the circular dependencies in class loading caused by loading the defaultSystemProvider.
liyazzi has updated the pull request incrementally with two additional commits since the last revision:
- Update the date of 'ImageReaderFactory'
- Update the date of 'ImageReaderFactory' and remove the import of 'Disabled' in SetDefaultProvider test
-------------
Changes:
- all: https://git.openjdk.org/jdk/pull/22628/files
- new: https://git.openjdk.org/jdk/pull/22628/files/ebf6b1da..7ee321b1
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jdk&pr=22628&range=08
- incr: https://webrevs.openjdk.org/?repo=jdk&pr=22628&range=07-08
Stats: 2 lines in 2 files changed: 0 ins; 1 del; 1 mod
Patch: https://git.openjdk.org/jdk/pull/22628.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/22628/head:pull/22628
PR: https://git.openjdk.org/jdk/pull/22628
More information about the core-libs-dev
mailing list