Last Updated: January 23, 1997
For Netscape Navigator versions 2.02 and 3.0
To install the plugin for Navigator, place npmsjava.dll in the .\program\plugins subdirectory of the Navigator installation tree (which is usually c:\program files\netscape\navigator). The location can be discovered programatically by querying the registry for the navigator installation directory.
To use the plugin inside of Netscape Navigator, you must use the <embed> tag. Here is a list of the <embed> tag attributes you will need to do this.
| Attribute | Description |
|---|---|
| src | The Java class file. |
| code | The Java class file. |
| codebase | basehref | Location of the Java class file. |
| type | Type of object to create. Value="application/java | application/ms-java" |
| width | Pixel coordinates for the width of the applet. |
| height | Pixel coordinates of the applet height. |
| param | Specifies the parameters for the applet. When the param keyword is found, it must be followed by the name= and value= attributes. |
| param_name | Parameter name for the applet. Must be followed by param_value. |
| param_value | Value of a parameter for the applet. |
<embed src="foo.class" code="myrealclass.class>
<embed src="bar.class" code="myrealclass.class>
In the above example, foo.class and bar.class are dummy files on the server (that contain at least one byte).
Navigator 3.0 - Using the TYPE Attribute
<embed type="appication/java" code="my.class" width=100 height=100 myparam="foo" myparam2="bar">
Navigator 3.0 - Two Applets Using the Same Class
<embed src="my.class" width=100 height=100 myparam=foo myotherparam=bar>
<embed src="my.class" width=100 height=100 myparam=baz myotherparam=zed>
Navigator 2.02 - Two Applets Using the Same Class
<embed src="dummy1.class" code="my.class" width=100 height=100 myparam=foo myotherparam=bar>
<embed src="dummy2.class" code="my.class" width=100 height=100 myparam=baz myotherparam=zed>
When this plugin is used with Netscape Navigator 2.02, some drawing and repainting problems have been reported. This is not a defect in the plugin, but rather is caused by the fact that Navigator 2.02 does not always instruct child windows to repaint when necessary. The Navigator release notes advise reloading or resizing the page to force a repaint in these cases. However, this is not a feasible option for a Java VM plugin.
The Microsoft VM for Java plugin utilize's its own network DLLs and cache. There is a known problem when navigating to a file URL and then an HTTP URL. There is a collision between the version of WinSock utilized by the plugin and the WinSock utilized by Netscape. To avoid this problem, always navigate to an URL first.
|
|