> >>I have no idea. One thing to point out is that the current implementation >>works for all releases preceding JDK 1.3 and no browser supports JDK 1.3 >>AFAIK. In fact, I don't believe there is any browser that supports any >>version of the JDK later than 1.1.x. Thus, it does not make a whole lot of >>sense to develop applets with JDK 1.3 unless you are willing to take the >>risk that you will inadvertently use features introduced after JDK 1.1.x. >I'm aware of this. It's a pain. The truely annoying thing, though, is that >when you develop an applet and run it in a browser, then modify the source, >compile, and hit the refresh/reload button on the browser it might still >load the applet before you modified it. I don't understand why this happens >and this is the reason why I use appletviewer when in the development stage. >I was a little surprised that others may develop applets differently, if >nobody has reported this bug yet. >Regards, >Daniel We've had some success getting around this problem by changing the settings on your web browser for when it compares documents in the cache. On netscape you can set it so that documents in the cache are compared to documents on the network every time, rather than once per session or never. This helps in getting the new classes loaded into the browser. I'm not sure if I have 100% confidence in this method but it did work for us. Ryan Chase
