JDK-7044944 : DT is not registered in Chrome if Firefox is not installed
  • Type: Bug
  • Component: install
  • Sub-Component: install
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2011-05-14
  • Updated: 2013-09-12
  • Resolved: 2011-09-15
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.
JDK 7
7u2Resolved
Related Reports
Duplicate :  
Relates :  
Description
If Firefox is not installed, the DT plugin is not getting registered with Chrome during JRE7 installation. 

IF Firefox is installed then Chrome will find it in the Firefox plugins but we can not expect Chrome users 
will have Firefox installed too.
This fix is rather localized/scope-restricted. Simple to test/verify as well a low risk and high impact for the client side: fine grain jre version detection in the Chrome platform is really required as this platform is ever growing in the market.
Pls approve.

Comments
EVALUATION This will be addressed with changes for 7088173.
15-09-2011

EVALUATION Preliminary webrev at http://oklahoma.east.sun.com/deployment/www/webrevs/cg207731/7044944/ Currently debugging.
08-06-2011

EVALUATION changing existing InstallDeployToolkit() function and removing existing Netscape/Mozilla/Firefox logic, replacing it with a call to RegisterDT() RegisterDT(): - gets the file version of npDeployJava1.dll, a.k.a. FF_TOOLKIT_DLL - CleanupFirefoxPlugins() removes older copies of FF_TOOLKIT_DLL from plugins directories under all Firefox installations - copies FF_TOOLKIT_DLL to Windows System directory unless a newer version of FF_TOOLKIT_DLL is already there - sets HKLM\SOFTWARE\MozillaPlugins\@java.com/DTPlugin, Path to C:\Windows\System32\npDeployJava1.dll
08-06-2011

EVALUATION Original design for this fix is to create a function called RegisterDT() in deploy.dll and fx installer and jre installer will call this function to get the acutall files we're going to delete/copy. It's not doable in this timeframe because we're constraint from the different compile configuration. Currently all installers are compiled with _UNICODE but deploy.dll are complied without this definition. Because of this, the command receive from deploy.dll can not interpret correctly in installer. We suggest to put all the code in installers for now and fix it correctly in 7-client code. Original webrev is in http://sa.sfbay.sun.com/projects/deployment_data/7/7044944.9/deploy/ What needs to be done in the installer is: - Grab RegisterDT() function and dependent things (macro/functions) - Still need to remove existing code to register Firefox DT plugin
02-06-2011

EVALUATION the current implementation to support DT is only copy npdeployJava1.dll to FF plugins directory. this is not good enough: 1. If FF is not installed, Chrome won't work. 2. plugins directory is not there for FF 4. To support DT on FF4 and Chrome, we need this fixed. FX2 deployment also depends on DT, for both webstart and browser applet.
18-05-2011