855155 wrote:Is the applet embedded in the HTML, or free floating?
..Can I deploy an applet with jnlp with signed jars and expect the applet to remain active even after the webpage has been changed or forwarded to a different view?
..I will have the applet/jnlp html code written dynamically every time and the onLoad() event will "expect" to find the applet fully active. ..AFAIU the 'onload' event is fired after all the HTML arrives, but does not include loading images, applets etc.
855155 wrote:It is, JWS could launch free-floating applets since it was introduced in Java 1.2, it is only since the Next Generation Plug-In2 architecture (Oracle's 1.6.0_10+ JRE) that JWS deployed applets can also be embedded. I'll take it from your answer that this applet is embedded.
.."embedded or free floating". I never knew the latter was possible. ..
..without forcing a browser destroy() call when the page is navigated or forwarded away from. ..I don't think that is possible. Or if it is, it would be taking advantage of a broken applet/browser implementation. Why is that necessary?
..Currently I successfully access the applet in a frameset and getting all that inter-process communication and syntax access to the applet methods by default, but prevents me from changing the client view. For development purposes I am deploying the applet in its own non-changing frame with the code below but that embeds it and is my "catch-22". I have tried Tiles..I'm not familiar with it, though I've heard the term used.
..and even jsp:include to change the desired client content and nothing works, without the browser calling destroy().BTW - are you sure that ends in valid HTML in the browser? The opening applet element is missing a closing '>' & has no '</applet>' to end it.
Therefore my dire need to load the applet(or redesign as an app) with jws, with syntax access to the methods that would simplify tremendously my client view deployment. Is/how this possible?
<bean:page id="context" property="request"/>
http://<bean:write name="context" property="serverName"/>:<bean:write name="context" property="serverPort"/><bean:write name="context" property="contextPath"/>/
<applet name="legacy" height="200" width="200" codebase="<bean:write name="myServletContext"/>" code="org.legacy.applet00"