JDK-8221180 : Deprecate AllowJNIEnvProxy
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 13
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-03-21
- Updated: 2019-03-28
- Resolved: 2019-03-21
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 13 |
|---|
13 b14Fixed  |
Related Reports
|
CSR :
|
|
|
Relates :
|
|
|
Relates :
|
Description
The product flag, AllowJNIEnvProxy, was added in JDK 6 by JDK-4881230 as the first step in the process of removing support for JNIEnv proxies (which the JNI spec forbids). It's unclear how long ago the need for JNIEnv proxies was removed, and more unclear when they would actually have stopped working. I have great confidence that the code has not worked for a very long time. So it is time to complete that process and remove the last remnants of JNIEnv proxy support. As AllowJNIEnvProxy is a product flag we will do the right think and initially deprecate it in JDK 13 and then obsolete in 14, then remove.