The AppletViewer doesn’t recognize the java_code, java_codebase, java_object, or java_type param tags.

The object tag recognized by IE4.n and the embed tag recognized by Netscape 4.n can be combined so that an applet can use the latest Java plug-in, regardless of the browser that downloads the applet. Other parameter tags are argument values supplied to the applet. For an applet, the value should be similar to:įor a serialized object or JavaBean, the type parameter value should be similar to: The type parameter tag isn’t used by AppletViewer, but should be present so that browsers load the plug-in properly. The optional codebase parameter tag supplies a relative URL that specifies the location of the applet class.Įither code or object is specified, not both.

The AppletViewer also ignores the codebase attribute that’s usually included as part of the object tag, assuming that it points to a Java plug-in in a network cab file with a value like: The AppletViewer ignores the classID attribute, on the assumption that it’s pointing to the Java plug-in, with the value:Ĭlassid='clsid:8AD9C840-044E-11D1-B3E9-00805F499D93'

Google java compiler online