Documentation Contents
lang="en-US" dir="ltr" xml:lang="en-US">

Java Rich Internet Applications Enhancement in JDK 7

The following topics are covered:

Enhancements in Java SE 7 Update 2

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

Enhancements in Java SE 7

In addition, the following enhancements are introduced:

Area: Deployment
Standard/Platform: JDK 7
Synopsis: 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: Deployment
Standard/Platform: JDK 7
Synopsis: 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: Deployment
Standard/Platform: JDK 7
Synopsis: 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: Deployment
Standard/Platform: JDK 7
Synopsis: As of JDK 7, clearing the cache works as follows:

RFE: 6873615

Area: JNLP Files
Standard/Platform: JDK 7
Synopsis: 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 Files
Standard/Platform: JDK 7
Synopsis: 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: Plugin
Standard/Platform: JDK 7
Synopsis: 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: Plugin
Standard/Platform: JDK 7
Synopsis: On Windows, the tray icon is now disabled by default. To enable the tray icon, use the Windows Start menu.
RFE: 6694710

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

Area: Plugin
Standard/Platform JDK 7
Synopsis: 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: Plugin
Standard/Platform: JDK 7
Synopsis: Google Chrome is now supported by the DT Plugin.
RFE: 6907245


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