United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-7165926 my .jar file can no long run by double-click under Windows Explorer.
JDK-7165926 : my .jar file can no long run by double-click under Windows Explorer.

Details
Type:
Bug
Submit Date:
2012-05-02
Status:
Closed
Updated Date:
2013-06-07
Project Name:
JDK
Resolved Date:
2012-05-03
Component:
install
OS:
windows_xp,windows_7
Sub-Component:
install
CPU:
x86
Priority:
P1
Resolution:
Fixed
Affected Versions:
7,7u4,7u6
Fixed Versions:
7u4 (b22)

Related Reports
Backport:
Backport:
Backport:
Duplicate:
Duplicate:
Duplicate:
Duplicate:
Duplicate:
Relates:

Sub Tasks

Description
I tried to move to 7u4 on Windows, and then discovers that all my .jar file can no long run by double-click under Windows Explorer.

                                    

Comments
EVALUATION

It looks like the regdeploy project introduced this regression on the install side.  These 2 lines were incorrectly removed from RegInstall.cpp:

        regMapEntriesCurrent[index].szKey = L"JARFILE_PARAM";
        regMapEntriesCurrent[index++].szData = A2OLE("\"%1\" %*");

when generating the RegCurrentVersion.rgs file, which looks like this:

HKCR
{
    ForceRemove .jar = s 'jarfile'
    {
    }
    ForceRemove jarfile = s 'Executable Jar File'
    {
            ForceRemove shell
            {
                ForceRemove open
                {
                        ForceRemove command = s '"%JAVAHOME%\bin\javaw.exe" -jar %JARFILE_PARAM%'
                }
            }
    }

    NoRemove Applications
    {
        ForceRemove 'java.exe'
        {
            val IsHostApp = s ''
        }

        ForceRemove 'javaw.exe'
        {
            val IsHostApp = s ''
        }
    }
}


HKLM
{
    NoRemove SOFTWARE
    {
            NoRemove JavaSoft
            {
                NoRemove 'Java Runtime Environment'
                {
                        val CurrentVersion = s '%FAMILY_VERSION%'
                }
            }
    }
}

This rgs file used to be riddled with plugin registries before we pruned them for the regdeploy project.   So I must have missed that the JARFILE_PARAM was still in the rgs file after taking the deploy stuff out.

It looks like the HKLM tree of the rgs file was applied correctly, which would have made the issue more obvious if it hadn't.  Only the HKCR part fails silently.
                                     
2012-05-03
Verified by Andy Chen at Evergreen.
                                     
2013-06-07



Hardware and Software, Engineered to Work Together