Example: Applet client tag requirements
Standard applets require the HTML <APPLET> tag to identify the applet to the browser. The <APPLET> tag invokes the Java™ virtual machine (JVM) of the browser. It can also be replaced by <OBJECT> and <EMBED> tags.
The following code example illustrates the applet code using the <APPLET> tag.
<APPLET code=”MyAppletClass.class” archive=”Applet.jar, EJB.jar” width="600" height="500" >
</APPLET>
The following code example illustrates the applet code using the <OBJECT> and <EMBED> tags.
<OBJECT classid="clsid: 8AD9C840-044E-11D1-B3E9-00805F499D93"
width="600" height="500">
<PARAM NAME=CODE VALUE=MyAppletClass.class>
<PARAM NAME="archive" VALUE='Applet.jar, EJB.jar'>
<PARAM TYPE="application/x-java-applet;version=1.5.0">
<PARAM NAME="scriptable" VALUE="false">
<PARAM NAME="cache-option" VALUE="Plugin">
<PARAM NAME="cache-archive" VALUE="Applet.jar, EJB.jar">
<COMMENT>
<EMBED type="application/x-java-applet;version=1.5.0" CODE=MyAppletClass.class
ARCHIVE="Applet.jar, EJB.jar" WIDTH="600" HEIGHT="500"
scriptable="false">
<NOEMBED>
</COMMENT>
</NOEMBED>WebSphere Java Application/Applet Thin Client for
Windows is required.
</EMBED>
</OBJECT>
Attention: To successfully invoke the applet client in WebSphere® Application Server version 6.1
or later, the <OBJECT classid and <EMBED
type values need to be those shown in the preceding example.
For more information about the <APPLET> tag, see Using applet, object and embed Tags.