< prev index next >

src/java.desktop/share/classes/sun/applet/AppletPanel.java

Print this page

        

*** 342,357 **** /** * Execute applet events. * Here is the state transition diagram * * Note: (XXX) is the action * APPLET_XXX is the state ! * (applet code loaded) --> APPLET_LOAD -- (applet init called)--> APPLET_INIT -- ( ! * applet start called) --> APPLET_START -- (applet stop called) -->APPLET_STOP --(applet ! * destroyed called) --> APPLET_DESTROY -->(applet gets disposed) --> ! * APPLET_DISPOSE -->.... * * In the legacy lifecycle model. The applet gets loaded, inited and started. So it stays * in the APPLET_START state unless the applet goes away(refresh page or leave the page). * So the applet stop method called and the applet enters APPLET_STOP state. Then if the applet * is revisited, it will call applet start method and enter the APPLET_START state and stay there. --- 342,359 ---- /** * Execute applet events. * Here is the state transition diagram * + * <pre>{@literal * Note: (XXX) is the action * APPLET_XXX is the state ! * (applet code loaded) --> APPLET_LOAD -- (applet init called)--> APPLET_INIT -- ! * (applet start called) --> APPLET_START -- (applet stop called) --> APPLET_STOP -- ! * (applet destroyed called) --> APPLET_DESTROY --> (applet gets disposed) --> ! * APPLET_DISPOSE --> ... ! * }</pre> * * In the legacy lifecycle model. The applet gets loaded, inited and started. So it stays * in the APPLET_START state unless the applet goes away(refresh page or leave the page). * So the applet stop method called and the applet enters APPLET_STOP state. Then if the applet * is revisited, it will call applet start method and enter the APPLET_START state and stay there.
*** 365,375 **** * * Also, the applet can jump from APPLET_INIT state to APPLET_DESTROY (in Netscape/Mozilla case). * Same as APPLET_LOAD to * APPLET_DISPOSE since all of this are triggered by browser. * - * */ @Override public void run() { Thread curThread = Thread.currentThread(); --- 367,376 ----
< prev index next >