Posted Wednesday, December 31, 1969 @ 23:59:59
I understand your frustration. I will help my best to resolve your problem.1) Exception: java.lang.ClassFormatError: com/smartdatasolutions/webapp/applets/QCGrid (Bad magic number).? exception.
If QCGrid is a applet class, then this is the first class loaded when you access the applet, so if you get this message during loading the first class, then you have a overall problem with your setup. Then this is not a problem with quicktable. But if QCGrid class is not an applet class and if this the class which uses quicktable and is instantiated in the applet class, then quicktable is the problem.
2) quicktable is compiled in jdk 1.2. But the default jdk available in browser is jdk 1.1. You are compiling your classes in jdk 1.4. If you really want to run the applet with the default jdk in browser , then you should compile all your classes in jdk 1.1, rather than jdk 1.4. The idea is, a jdk can use the classes compiled using the jdk version less than or equal to its version. so if you use 1.4 classes in jdk 1.1 it won't work. If you really want to use jdk 1.4, then there is no other option than using a java plugin. Have a look at the url http://java.sun.com/products/plugin/index-1.4.1.html to learn about plugin.
3) Please make sure you have ftped the file to server in binary mode.
If you are using the Quicktable jar file (instead of extracting the classes ) in the applet html, then you have ftped correctly. But if you have extracted the class files, then make sure you have ftped the class files to webserver in binary format. If that is incorrect, then Replace your class binary files on the web server, clean up (important) the cache of your browser, and reload your applet.
4) I've found that this error is caused by the web server giving
either an error message (like 404) or a strange MIME type for the class when
it returns the class. Sometimes the browser returns the class as text rather than binary, If you enter the URL for your applet class into
the browser directly, what does the server respond, and how does the
browser react? (ie: if your web page is http://www.somecompany.com/SomePage.html
and your class is SomeClass.class, then request http://www.somecompany.com/SomeClass.class
and see what you get.) I prefer using a MIME type like "application/octet-stream"
for class files.