Java Plugin

Bei dieser Anwendung wird explizit Java 1.5 (Version 5) angefordert, da die integrierte RMI-API diese Version benötigt. Ist es nicht im Browser vorgesehe, wird ein Versionkonflikt gemeldet. Hier das Demo-Beispiel:

Parameter des Plugins

name="file" value="<svgFileUrl>"

URL der svg-Datei des Friedhofs z.B: file:currTest.svg.

name="menu" value="on|off"

Einblenden der Menüleiste. Default ist off.

name="toolbar" value="on|off"

Einblenden der Toolbar. Default ist on.

name="propPanel" value="on|off"

Einblenden des Fensters mit der Attributausgabe. Default ist off.

name="debug" value="on|off"

Einschalten der Debug und Traceausgaben. Sie werden mit log4j ausgeführt, wobei das Standardausgabeformat angewendet wird, da für Applets der Zugriff auf lokale Dateien verwehrt ist. Default ist off.

Bei Parametern mit Schalterfunktion (on|off) werden alle Eingaben außer on oder ON werden als off interpretiert.

Vorteile des Plugins

Kopie aus der Sun Dokumentation:

Other Enhancements

In addition to the support for the APPLET tag described above, the Java Plug-in has many performance and architecture enhancements that will make it more suitable for widespread use on consumer client machines that typically are not as powerful as client platforms in an enterprise environment. Some of these enhancements are summarized below.

Memory management

• Dynamic maximum heap size is scaled down from 128 MB to 96MB to avoid unnecessary paging on the system.
• Classloader implementation has been tuned to allow memory to be reclaimed more often by the garbage collector.
  
• Potential memory leak issue is addressed by using JNI/COM smart pointers in implementation.

Performance

• Applet download time is significant reduced by relying on browser caching when possible. No connection will be opened on the server side unless it is absolutely necessary.
• Applet lifecycle is controlled asynchronously to allow very fast page switch.
• Sped up classloader object reclaim by removing its finalize() method.
• HTTPS read has been made significantly faster by increasing buffer size.
• HTTPS calls are significant faster by statically linking Microsoft's Wininet instead of dynamic function lookup every time.
• JavaScript performance is greatly enhanced by eliminating BeanInfo lookup over the network.
• Java Console performance is enhanced by using the Console Writer thread to avoid blocking System.out and System.err when possible.

Status der Applet-Technologie

Kopie aus der Sun Dokumentation:

Using the applet tag

You use the applet tag to deploy applets to a multi-browser environment.

For complete details on the applet tag, read the W3 HTML specification.

Note: The HTML specification states that the applet tag is deprecated, and that you should use the object tag instead. However, the specification is vague about how browsers should implement the object tag to support Java applets, and browser support is currently inconsistent. Sun therefore recommends that you continue to use the applet tag as a consistent way to deploy Java applets across browsers on all platforms.

Following is an example of the applet tag:

<applet code=Applet1.class width="200" height="200">
Your browser does not support the <code>applet</code> tag.
</applet>

For both Internet Explorer and the Mozilla family of browsers, if Java Plug-in is installed (version 1.3.1_01a or later) then the highest installed version of Java Plug-in is invoked to run the applet.

Note: You cannot use the applet tag to automatically download a JRE if one is not installed locally.