JDK-8037400 : Remove getInitialMap getters and GlobalObject interface.
- Type: Bug
- Component: core-libs
- Sub-Component: jdk.nashorn
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2014-03-14
- Updated: 2014-07-29
- Resolved: 2014-03-17
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 8 | JDK 9 |
|---|---|
8u20Fixed  |
9 b06Fixed |
Description
* nasgen generated maps are mostly used only with the current class (after recent class sharing changes). getInitialMap package-private accessors can be removed. * GlobalObject was a way to shield classloader boundary (in the past jdk.nashorn.internal.objects.* were loaded by a different loader and hence runtime can't refer to Global class). This is not needed anymore. Also Context.getGlobal/setGlobal can use Global type and avoid Global/GlobalObject cast in many places.