Quiz software, teaching tools, exam revision aids, learning games, courseware authoring
Java Menus
Java menu homeJava downloadBuy a java menuJava menu help centreContact us
Java menus » Java menu knowledge base

 SEARCH

 MENUS BY TYPE

 Drop-down menus

 Animated buttons

 Tree menus

 Sliding menus

 Tab menus

 Image maps

 MENUS BY NAME

 X-Bar menus

 iPOP menus

 iSlide menus

 iTree menus

 iTab menus

 iMMap menus

 Sensomap menus

 Magic menus

 MENU DESIGN

 Menu design

 Drop-down menus

 Web buttons

 Tree menus

 Sliding menus

 Menu tabs

 Image maps

 SITE LINKS

 Home

 Java downloads

 Prices / Buying

 Support

 Company

 Contact

 New menus

 Free menus

 PARTNER SITES

 Alien Menus

 Happy Menus
Java menu knowledge base
BeanInfo and COMClassObject in error log
Return to knowledge base directory

 
Missing BeanInfo.class and/or $COMClassObject.class
 
Server administrators often notice that applets of all kinds tend to throw two different kinds of "file not found" reports into the error log.
 
These are harmless and should be ignored!
 
Information at Microsoft (Microsoft Knowledge Base Article 243771) explains that for various reasons of its own, all applets using the Microsoft Java Interpreter (possibly certain browser versions only) are required to check the server in case there is a *BeanInfo.class file with the applet. If there is no such file (and most applets won't have one), then the Microsoft Java Interpreter simply creates a replacement by itself and continues to function perfectly normally. The purpose of the *BeanInfo.class is so unusual and rare it is not even worth explaining here (you can read the Microsoft articles if you are curious). Just don't worry about it.
 
Microsoft does not appear to explain the $COMClassObject.class mystery (which sometimes appears along with the BeanInfo.class error). However the explanation they give for the BeanInfo.class would seem to be relevant to this as well.
 
If your server administrator doesn't like the error log reports, s/he would be best advised to modify the .htaccess file or equivalent to suppress the reports. However you are not advised to interfere with the server request itself - the best thing the server can return is a "not found" code.
 
java menu