This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hello Is it possible to fully unload an applet from its destroy fully? I need the second instantiation of the applet to be loaded de novo, as if for the first time, even if just the back button on the browser was click. Can I hook some shutdown hook to fully eliminate the applet from the browser cache, and make it start "virginally" the next activation in the same browser session, without loosing the browser session? tia.
What would be the difference between executing the destroy method and "fully eliminating" the applet?
Joined: Aug 27, 2005
Originally posted by Ulf Dittmer: What would be the difference between executing the destroy method and "fully eliminating" the applet?
It appears that it is still in the cache. I need to configure it to fully shutdown and restart the jvm, if possible without closing the browser. I know I can unload a SE application by hooking the shutdown hook and realize that is similar to destroy(), however I really want to restart the jvm in the browser.
Joined: Mar 22, 2005
I don't think there is a way to restart the JVM. It generally stays active until the browser is closed. And unless the client-side jar file cache is disabled, it would also reuse the applet jar file.
But why would that be a problem - does the applet use class initializers that do something different on each invocation, or make use of finalizers? If the former, could you move that code to object constructors or the applet's init method?