JDK-8080955 : embedded_jnlp param requires also code or jnlp_href param or applet arg.
- Type: Bug
- Component: deploy
- Sub-Component: plugin
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-05-22
- Updated: 2015-09-29
- Resolved: 2015-05-26
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 |
|---|---|
8u60 b18Fixed  |
9Fixed |
Description
The option to embed the jnlp file in a web page was added in JDK7, to optimize launching jnlp applets.
The parameter (or applet arg) was added to neither the list in:
src/plugin/share/plugin2/npjp2/NPAPIJavaPlugin.cpp, nore the code in
src/common/share/classes/com/sun/applet2/AppletParameters.containsAppletCode()
as a result, you still need one of {jnlp_href, code, object, java_code} to launch an applet.
Oracle forms has reported that it was necessary to add jnlp_href="foo.jnlp", to their applet html page when using embedded_jnlp, and that the file at codebase/foo.jnlp would be downloaded and applet would fail if it were not there.
This is contrary to the purpose of embedded_jnlp, and was only caused by the oversight of not adding it to the two lists (one is for IE, the other is for Mozilla based browsers) to allow applet to run if one of the items is there.
Comments
|