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.

• For applets to communicate with Enterprise Java Beans (EJB) in the WebSphere Application Server environment, the <APPLET> tag must be replaced with the following tags:

  <OBJECT>
  <EMBED>

• The classid and type attributes cannot be modified, and must be entered as described in the applet client example. The codebase attribute on the <OBJECT> tag must be excluded. Do not confuse the codebase attribute on the <OBJECT> tag with the codebase attribute on the <PARM> tag. Although both attributes are called codebase, they are separate entities.

• The following code example illustrates the applet code. In this example, MyApplet.class is the applet code, applet.jar is the file that contains the applet code, and EJB.jar is the file that contains the enterprise bean code:

  <OBJECT classid="clsid:8AE2D840-EC04-11D4-AC77-006094334AA9"
  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.3">
  <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-websphere-client" 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>

• The value of the type attribute on the </EMBED> tag can also be, for example:

  <EMBED type="application/x-websphere-client, version=4.0" ...

    

 

---