JDK-8057164 : Remove dead code
- Type: Sub-task
- Component: deploy
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2014-09-03
- Updated: 2015-09-29
- Resolved: 2015-05-12
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 |
|---|---|
8u60Fixed  |
9 b68Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
1.) With the fix of security vulnerability JDK-8052111 , The cached result of security validation is no longer used, and all jars are properly validated on subsequent runs as they are on the first run. There is still a lot of code in JNLPSignedResourcesHelper, SigningInfo, and CacheEntry to record the validation results and time information in the cache. We should clean up all such code that is no longer being used (being careful to consider which information is used intra-run to avoid multiple validations of the same jar in one run of an applet or applet). 2.) Java Web Start still has a JNLPPreverifyClassLoader (used only for unsupported versions of JavaFX) and a PreverificationClassLoader (used for applications and extensions imported into the system cache). Both these class loaders and lots of related code could be removed to clean up code.
Comments
|