JDK-8037518 : Unit Test Failures due to RDF and other 8u5 changes.
- Type: Bug
- Component: deploy
- Affected Version: 8u20
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2014-03-17
- Updated: 2014-10-15
- Resolved: 2014-03-18
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 7 | JDK 8 | JDK 9 |
|---|---|---|
7u71Fixed  |
8u20Fixed |
9 b08Fixed |
Description
After porting 8u5 changes into JDK9 (including DRDF feature) - I notice several additional unit test failures:
1.) several tests get NPE in LaunchDesc.getSource().
It is required that _xmlnode be non-null, but several unit test create LaunchDesc with null XmlNode, and this is now called from LaunchDesc.getAppInfo() (getSource was not called from getAppInfo till RDF feature)
2.) several tests assume all no-href jnlp files will be cached as ".jarjnlp". This assumption is no longer valid, as in some cases, LaunchDesc.getCanonicalHome() will return the original url used to launch an applet.
Comments
|