Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.fsmpi.rwth-aachen.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Knute Johnson Newsgroups: comp.lang.java.programmer Subject: Re: What would stop Applet from re-loading after page refresh? Date: Thu, 18 Jul 2013 17:42:28 -0700 Organization: A noiseless patient Spider Lines: 32 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Fri, 19 Jul 2013 00:36:25 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="aba33539224e5c782fe0c4053f7756fd"; logging-data="8544"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+98Ye39Nuc9+grAw+KGMmx" User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 In-Reply-To: Cancel-Lock: sha1:aGUyri4o9D7Yrar4YLNTM609ZN4= Xref: csiph.com comp.lang.java.programmer:24754 On 7/18/2013 7:36 AM, Richard Maher wrote: > Hi, > > I have an Applet that is loaded dynamically at run-time with the > tag loaded into a DIV with innerHTML. Everything seems peachy > and all works well until I refresh the page and then after what appears > to be a very successful destroy() method, I get nothing more in the Java > console with logging set to 5. My own console.log() message in > Javascript tell me the ERROR java_status_event is called when trying to > reload the Applet (no init() activity). > > Via a simple SSCcE I tested STATIC variable LiveConnect/JSObject, > SYNCHRONIZED Methods, and delaying the destroy() but the light versions > all refresh and reload without issue. (BTW there is no on-screen > footprint/output for the Applet). > > So my question is does anyone have an idea what is causing the > full-version of the Applet to have problems reloading on a refresh? > > Is there something being left-behind that is stopping the new version? > > Cheers Richard Maher > > PS. Classloader cache is shared/default. There are additional Threads > created. It is unsigned and sand-boxed. Java 7. What exactly do you do in the destroy() method? Have you tried not destroying it? -- Knute Johnson