JDK-6618971 : Plugin2: Legacy lifecycle support needs to be added
  • Type: Bug
  • Component: deploy
  • Sub-Component: plugin
  • Affected Version: 5.0,6u5
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2007-10-19
  • Updated: 2010-09-08
  • Resolved: 2008-01-25
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
6u10 b09Fixed
Related Reports
Relates :  
Legacy lifecycle support needs to be added the new Plug-in model. With legacy_lifecyce tag set to true, init() and constructor should get called once (for the first time), not when page is refreshed or swtiched back or forward and destroy should get called only and only when browser session is closed.

SUGGESTED FIX http://sa.sfbay.sun.com/projects/deployment_data/6u10/6618971.2 testcase: http://web-east.east.sun.com/deployment/www/tests/1.6.0_10/6618971/

EVALUATION Added support for the legacy applet lifecycle to the new Java Plug-In. Improved upon the implementation in the old plug-in: added support for caching multiple identical applets on the same web page, made the caching more precise by including the document base in the caching criteria, and added a watchdog timer to flush cached applets when memory pressure is high. Out of necessity, added support for getDocumentBase to IExplorerPlugin. Fixed preexisting bug in MozPluginInstance where the document base it was producing wasn't semantically correct. Fixed preexisting bug in code which detected still-visible top-level windows during AppContext disposal. Added "normalization" of document base because the URL coming from web browser wasn't the same as when we constructed a URL and then called toString() on it. Tested with new mostly-automated test cases in both Internet Explorer and Firefox 3.