The information in this article applies to:
If an HTML file uses an <OBJECT> tag to include an applet, specifies a class library for that applet to use via the three useslibrary parameters, and there is no codebase parameter to completely specify the applet's codebase, the <OBJECT> tag will fail to load the library. If Java logging is enabled, the following message occurs in the Java log or the Java console:
USESLIBRARYCODEBASE, no base URL
The CODEBASE attribute of the <OBJECT> tag has no effect.
Specifying a fully qualified URL for the codebase via a codebase *parameter* enables the <OBJECT> tag to work as expected. If a fully qualified codebase URL is specified, then both the useslibrary install and the regular object loading operate successfully.
Note You must specify the codebase as a param; placing a codebase attribute inside the <OBJECT ...> block has no effect at present. For example:
<object classid="java:MyApplet" height=240 width=320> <param name=codebase value=http://myserver/myfolder> <param name=useslibrary VALUE="MyPackageName"> <param name=useslibrarycodebase VALUE="MyPackage.cab"> <param name=useslibraryversion VALUE="1,0,0,1"> </object>
Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article.
This bug was corrected in the Microsoft VM contained in the SDK for Java 3.0 and later.
The codebase must be specified as a parameter, not as an attribute of the <OBJECT> tag, and it must fully specify the folder in which the applet classes and library .cab file reside.
Further information about libraries can be found in the documentation for the Microsoft SDK for Java, version 2.01, at the following address:
http://www.microsoft.com/java/sdk/20/default.htm .
For the latest Knowledge Base articles and other support information on Microsoft® Visual J++® and the SDK for Java, please see the following pages on the Microsoft Technical Support site:
http://support.microsoft.com/support/visualj/
http://support.microsoft.com/support/java/
codebase url object tags