-
Bug
-
Resolution: Fixed
-
P4
-
1.4.0
-
hopper
-
x86
-
windows_98
-
Not verified
Name: gm110360 Date: 02/28/2002
FULL PRODUCT VERSION :
java version "1.4.0"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.0-b92)
Java HotSpot(TM) Client VM (build 1.4.0-b92, mixed mode)
FULL OPERATING SYSTEM VERSION :
Windows Millennium [Version 4.90.3000]
A DESCRIPTION OF THE PROBLEM :
I had an existing installation of 1.3.1 JDK installed, and
it worked perfectly. The JDK was installed in c:\jdk1.3.1
and the included JRE was installed in the default
subdirectory under C:\program files\ . I recently installed
the new 1.4.0 JDK in C:\java and its associated JRE went in
C:\program files\Java\j2re1.4.0 . This new JDK worked
perfectly. Then I decided to remove the old 1.3.1 JRE since
I was moving all my development over to the 1.4.0 platform.
I removed the 1.3.1 JRE using the "Java 2 Runtime
Environment, SE 1.3.1" item in the Add/Remove Programs
Control Panel. Immediately after I removed the 1.3.1 JRE,
all .jar files lost their association with javaw.exe. I was
no longer able to double click on a .jar file and have it
execute.
Even worse, however, is that I have tried to repair the
problem by re-associating .jar files with the correct
command, and it still does not work. My current Open action
for .jar files is this: ' "C:\Program Files\Java\j2re1.4.0
\bin\javaw.exe" -jar %1 ', but double clicking on .jar
files does not open them. There appears to be some
temporary activity, as the cursor changes to the 'busy in
background' cursor, but Javaw quickly exits without
accomplishing anything and is no longer visible in the task
list.
I believe this problem may be related to the many closed
bugs that refer to Registry key corruption. I respectfully
suggest that this issue has not gone away, and a tool or
program absolutely needs to be made available that will
repair the corruption caused by the JRE's uninstall program.
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Install JDK 1.3.1
2. Install JDK 1.4.0.
3. Uninstall the 1.3.1 JRE included with the 1.3.1 JDK.
EXPECTED VERSUS ACTUAL BEHAVIOR :
The JRE silently started and stopped, without showing an
error message or executing any code.
This bug can be reproduced always.
CUSTOMER WORKAROUND :
N/A: Java files can, of course, be executed without double
clicking on them, but what's the point of having an
Executable Jar if it is not associated with the Java
launcher?
(Review ID: 143495)
======================================================================