Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8038863 | 9 | Raymond Gallardo | P3 | Closed | Fixed |
The link to the JNLP specification is broken:
http://www.oracle.com/technetwork/java/javase/download-spec-142476.html
It's probably gone from OTN.
Add this to the Java SE Developer Guides.
For now, I removed references to the JNLP specification from the following places:
http://docs.oracle.com/javase/8/docs/technotes/guides/jweb/applet_migration.html
<p>If you want to deploy extensions for your Java Web Start application, use the JNLP extension protocol mechanism. For more details, refer to the <a href="http://www.oracle.com/technetwork/java/javase/download-spec-142476.html">JNLP specification</a>, section 3.8 "Extension Descriptor."</p>
<p>For signed JAR files, similar to Java Plug-in technology, you can sign your application JAR files and request your application to be run with all-permissions by means of the JNLP file. In Java Plug-in technology, your applet JARs can be signed by different certificates. In Java Web Start technology, the same certificate must be used to sign all JAR files (<code>jar</code> and <code>nativelib</code> elements) that are part of a single JNLP file. This simplifies user management since only one certificate must be presented to the user during a launch per JNLP file. If you need to use JARs signed with different certificates, you can put them in a component extension JNLP file, and reference it from the main JNLP file. For more details, refer to the <a href="http://www.oracle.com/technetwork/java/javase/download-spec-142476.html">JNLP specification</a>, section 5.4 "Signed Applications" and section 4.7 "Extension Resources."</p>
http://www.oracle.com/technetwork/java/javase/download-spec-142476.html
It's probably gone from OTN.
Add this to the Java SE Developer Guides.
For now, I removed references to the JNLP specification from the following places:
http://docs.oracle.com/javase/8/docs/technotes/guides/jweb/applet_migration.html
<p>If you want to deploy extensions for your Java Web Start application, use the JNLP extension protocol mechanism. For more details, refer to the <a href="http://www.oracle.com/technetwork/java/javase/download-spec-142476.html">JNLP specification</a>, section 3.8 "Extension Descriptor."</p>
<p>For signed JAR files, similar to Java Plug-in technology, you can sign your application JAR files and request your application to be run with all-permissions by means of the JNLP file. In Java Plug-in technology, your applet JARs can be signed by different certificates. In Java Web Start technology, the same certificate must be used to sign all JAR files (<code>jar</code> and <code>nativelib</code> elements) that are part of a single JNLP file. This simplifies user management since only one certificate must be presented to the user during a launch per JNLP file. If you need to use JARs signed with different certificates, you can put them in a component extension JNLP file, and reference it from the main JNLP file. For more details, refer to the <a href="http://www.oracle.com/technetwork/java/javase/download-spec-142476.html">JNLP specification</a>, section 5.4 "Signed Applications" and section 4.7 "Extension Resources."</p>
- backported by
-
JDK-8038863 Missing JNLP specification
- Closed