JDK-4640775 : windows installer should verify jnlp file association
  • Type: Bug
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: 1.0.1
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: windows_2000
  • CPU: x86
  • Submitted: 2002-02-21
  • Updated: 2002-08-22
  • Resolved: 2002-08-22
Related Reports
Duplicate :  
Description

Name: nt126004			Date: 02/20/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 2000


EXTRA RELEVANT SYSTEM CONFIGURATION :
ie 6.0, ultraedit installed

A DESCRIPTION OF THE PROBLEM :
Another application on my machine associated itself with
the jnlp file extension. The jdk 1.4.0 installer does not
notice this and does not fix it either. Consequently,
webstart links don't work.

If you don't know this, it is hard to fix. The application
that registered itself for jnlp was ultra edit (I wasn't
able to reproduce it though).

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Associate some application with jnlp (for example ultra edit)
2. Install jdk 1.4.0
3. Click on a jnlp link

EXPECTED VERSUS ACTUAL BEHAVIOR :
I expected webstart or the installer to detect and fix the
file association (after asking what to do of course).

Instead it just failed to notice. IE displayed a save as
dialog. Discovering what the issue is took a long time
since all registry settings seem normal. Only when I saved
the jnlp file I noticed the ultra edit icon. After that I
knew what was going on.

This bug can be reproduced always.

CUSTOMER WORKAROUND :
fix the file associating by shift right clicking on a jnlp
file (e.g. saved with said dialog), choose "open with"
rather than "open" and pick javaws and toggle the always
use this application checkbox.
(Review ID: 139689) 
======================================================================

Comments
EVALUATION This is probably a bug, let's investigate for Mantis. ###@###.### 2002-07-23 This will be fixed when we move to Installshield 7.0 ###@###.### 2002-08-22
23-07-2002