JDK-8257853 : Remove dependencies on JNF's JNI utility functions in AWT and 2D code
- Type: Bug
- Component: client-libs
- Sub-Component: java.awt
- Affected Version: 17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-12-07
- Updated: 2021-07-16
- Resolved: 2020-12-19
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 11 | JDK 13 | JDK 15 | JDK 17 |
|---|---|---|---|
| 11.0.12-oracleFixed | 13.0.8Fixed | 15.0.4Fixed | 17 b03Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
We can address uses of JNF_CTOR_CACHE, JNF_CLASS_CACHE and JNF_MEMBER_CACHE, JNF_STATIC_MEMBER_CACHE and associated JNFNewObject and JNFCall* methods to directly use JNI. Elsewhere in the desktop module this kind of thing is often done in a static method called by class initialisation. To reduce the size of source code changes and make reviews easier we can define a small set of macros which achive the same benefit of the *CACHE macros - ie avoiding repeated JNI lookups.
Comments
|