JDK-4531885 : Improved JNLP url support in application manager
  • Type: Enhancement
  • Component: deploy
  • Sub-Component: webstart
  • Affected Version: jaws-1.0,1.0,1.0.1,1.2.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS:
    generic,solaris_2.6,windows_98,windows_nt generic,solaris_2.6,windows_98,windows_nt
  • CPU: generic,x86,sparc
  • Submitted: 2001-11-27
  • Updated: 2002-10-15
  • Resolved: 2002-10-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.
Other
1.4.2 mantisFixed
Related Reports
Duplicate :  
Duplicate :  
Duplicate :  
Description

Name: nt126004			Date: 11/27/2001


java version "1.3.1"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.1-b24)
Java HotSpot(TM) Client VM (build 1.3.1-b24, mixed mode)


JNLP URLs ought to be directly openable from the Java Web Start application
launcher.  this would allow programs to launch even from servers that aren't
properly set up to serve the JNLP mime type.

you would just have a "File" -> "Open URL" type menu item in which you could
type http://servername/filename.jnlp.  this would get around situations
where your server wasn't set up to properly specify the MIME type to make
Java Web Start handle JNLP files.  for example, on my ISP's server :-)  i
can create a JNLP file, but if i create a link to it, it doesn't trigger
Java Web Start.  so... it would be nice to be able to tell people the direct
URL and let them copy & paste it into Java Web Start directly.  i also ran
into this situation over the past few weeks trying to download another
party's JNLP application before they had their server set up properly.  the
JNLP file would just load as text in my browsers and i couldn't get to the
application at all :-(

this would also get around situations where your browser might not be set up
properly for the JNLP MIME type (e.g. strange browser or corrupted
configuration).  finally, it would, indeed, be useful to load local JNLP
files for testing.
(Review ID: 135394) 
======================================================================

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: mantis FIXED IN: mantis INTEGRATED IN: mantis mantis-b04
31-08-2004

EVALUATION fixed for hopper although from a browser, you still need the web-server to have the jnlp mime type set correctly, this is no longer necessary from java web starts point of view. You can now run: javaws http:server.com/myfile.jnlp when the server server,com is not set up with the java web start mime type. If you set the remote apps url in the application manager a page with a link to http:server.com/myfile.jnlp, then that app will show up in the application manager and can be launched from there. ###@###.### 2002-02-11 Although no menu item "Open url", I think the remaining part of this rfe will be implemented by the AppMan change to move the remote url location bar to the main page of appman. So I am re-assigniong to Thomas, and committing to mantis. ###@###.### 2002-07-22 This will be implemented by moving the remote url combo box to the main page of application manager. The combo box will accpet either a html file with list of jnlp hrefs or just a single jnlp file url. This provide a better accessibility to the remote url combo box (similar to a web browser experience). ###@###.### 2002-07-30
30-07-2002