🔒 Locked

[java] Applet Problems

Started by Tokiko Nov 6, 2004 at 8:37 PM 5 replies 800+ views

Original Post

Nov 6, 2004 at 8:37 PM

I just tried out applets and everything is working great, however whenever I change something in my code and recompile, the applet wont change in my browser. I tried deleting the applet and my browser still displays the original. Im guessing the class file stays in some temp folder or cache, so how do I fix this? I deleted my browsers cache, and Java's cache and it still loads. It is very annoying having to change the file name every time I want to see my code changes. Thanks.

Tokiko

Nov 6, 2004 at 8:50 PM

Well for some reason Im only having this problem with Firefox. It's working fine with Mozilla, but im still curious if anyone knows what the problem is with firefox.

Koroljov

Nov 7, 2004 at 1:05 AM

Do you close the browser and reopen it? Or do you just reload the page?

In internet explorer, it is often necesary to close the browser and reopen it.

tjoink

Nov 7, 2004 at 2:29 AM

Yes, this is a problem. You either have to restart the browser (all sessions), or you can open the Java Plugin Console window. (Right click on it in the sys tray -> open console.) Then, after recompiling, press x (clear classloader cache), f (finalize objects on finalization queue), then refresh the browser. It will load the new applet class.

capn_midnight

Nov 7, 2004 at 8:03 AM

Quote:
Original post by Anonymous Poster
In 99% of cases, the single key press to clear java class cache is all that is necessary.

In most cases these days, this whole problem only occurs because of shitty broken webcaches whcih you just have to suck it down. Bastard ISP's too damn stupid to configure Squid etc properly. I saw one ISP who any file you changed on their server that was NOT .htm took 18 hours to update (because they had a local cache in front of it with a broken clock)

Haha! Was it a Mac server? I worked with one that wouldn't update images until the admin manually cleared the cache. The stupid server also distinguished between:
http://www.blah.com/blah/ and
http://www.blah.com/blah
where the latter would be connected on a different port than HTTP.

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.