Documentation Contents
Java Platform, Standard Edition Deployment Guide
Contents    Previous   

34 Java Rich Internet Applications Enhancements in JDK 7

This chapter provides an overview of new and changed deployment features in JDK 7.

The following sections describe the improvements and the release in which they were introduced.

34.1 Enhancements in JDK 7 Update 51

The JDK 7u51 release includes the following enhancements:

34.2 Enhancements in JDK 7 Update 45

The JDK 7u45 release includes the following enhancements:

34.3 Enhancements in JDK 7 Update 40

The JDK 7u40 release includes the following enhancements:

In addition, Chapter 24, "Rich Internet Application Deployment Process" provides a look at how the deployment of RIAs is handled.

34.4 Enhancements in JDK 7 Update 25

The JDK 7u25 release includes the following security enhancements:

In addition, the Section 23.5, "Security Dialogs" section provides information on the prompts that are shown when a RIA is started, and Deployment Best Practices in the Java Tutorial provide suggestions for deploying your RIA.

34.5 Enhancements in JDK 7 Update 21

This release includes the following security enhancements for running rich internet applications (RIAs), which are Java applets and Java Web Start applications:

34.6 Enhancements in JDK 7 Update 10

The JDK 7u10 release includes the following enhancements:

  • The ability to disable any Java app from running in the browser. This mode can be set in the Java Control Panel or using a command-line install argument (Microsoft Windows only).

  • The ability to select the desired level of security for unsigned applets, Java Web Start applications, and embedded JavaFX applications that run in a browser. Four levels of security are supported. This feature can be set in the Java Control Panel, or using a command-line install argument (Microsoft Windows only).

  • New dialogs warn you when the JRE is insecure (either expired or below the security baseline) and needs to be updated.

For more information, see Chapter 23, "Setting the Security Level of the Java Client" and Chapter 20, "Java Control Panel.".

34.7 Enhancements in JDK 7 Update 6

This release includes Oracle's release of the JRE and JDK for the Mac. Here is related information:

34.8 Enhancements in JDK 7 Update 2

This release introduces the following improvements for web-deployed applications:

34.9 Enhancements in Java SE 7

In addition, the following enhancements are introduced:

Area: DeploymentStandard/Platform: JDK 7Synopsis: Previously, the pack200 tool segmented its output by default. As of this release, the pack200 tool will create one large segment per jar file. Therefore, if deployers have jar files larger than the virtual memory available on the end-user's systems, it is recommended that either the input jar file be split, or suitably segmented by using the command-line flag "--segment-limit=nnnnn" or the equivalent property "SEGMENT_LIMIT".RFE: 6575357

Area: DeploymentStandard/Platform: JDK 7Synopsis: On Windows XP machines, the default cache directory is now under $USER\Local Settings\Application Data\Sun\Java\Deployment\cache. If needed, you may customize it to point to a network share folder for a single application cache across domain machines.RFE: 7012538

Area: DeploymentStandard/Platform: JDK 7Synopsis: The optional applet parameter, jnlp_embedded, provides the option to cache JNLP content on the HTML page and shortens applet launch time by skipping network access. The jnlp_embedded parameter has as its value the base64 encoded content of the applet JNLP file. For example:

<applet width="710" height="540" >
 <param name="jnlp_href" value="launch.jnlp"/>
 <param name="jnlp_embedded"
 value="PD94bWwgdmVyc2lvbj0iMS4wIiB . . . dC1kZXNjPg0KPC9qbmxwPg0K"/>
 <param name="draggable" value="true"/>
</applet>

When present, the jnlp_embedded parameter value replaces the content of the JNLP value pointed to by the jn.p_href parameter. The value of jnlp_ref is then optional and only used as a backup when the content of jnlp_embedded is invalid. There are a few restrictions on the embedded JNLP content:

RFE: 6990877

Area: DeploymentStandard/Platform: JDK 7Synopsis: As of JDK 7, clearing the cache works as follows:

RFE: 6873615

Area: JNLP FilesStandard/Platform: JDK 7Synopsis: In order to support debugging of Java Web Start applications, the -XX:HeapDumpOnOutOfMemoryError flag is now supported in JNLP files for trusted applications.RFE: 6664424

Area: JNLP FilesStandard/Platform: JDK 7Synopsis: Previous versions of Java Web Start did not correctly implement section 6.0.10 of the JNLP Specification. With this fix, fine-grained values for the "os" attribute, such as os="Windows\ XP", os="Windows\ Vista", and os="Windows\ 7", will work as expected. Values such as os="Win", and os="Windows" will continue to match all Windows platforms. As of this release, os="Windows\ Vista Windows\ 7" will only match Vista or Windows 7 and not Windows XP.RFE: 7014170

Area: PluginStandard/Platform: JDK 7Synopsis: A message stating that the first generation of the Java plugin is deprecated is now printed to the log file and to the Java console whenever plugin 1 is used.RFE: 7027792

Area: PluginStandard/Platform: JDK 7Synopsis: On Windows, the tray icon is now disabled by default. To enable the tray icon, use the Windows Start menu.RFE: 6694710

Area: PluginStandard/Platform: JDK 7Synopsis: The 64-bit toolkit is now supported on 64-bit Windows platforms.RFE: 6492139

Area: PluginStandard/Platform JDK 7Synopsis: Previously, the persistence API provided only temporary persistence for applets. When the VM exited, the data was lost. Data can be persisted via any of the standard Java mechanisms, through the use of LiveConnect to store data in the page DOM, or using one of the JNLP services.RFE: 6992419

Area: PluginStandard/Platform: JDK 7Synopsis: Google Chrome is now supported by the DT Plugin.RFE: 6907245

Contents    Previous   

Oracle and/or its affiliates Copyright © 1993, 2015, Oracle and/or its affiliates. All rights reserved.
Contact Us