Bug 127562

Summary: Java Web Start not configured/working by default in firefox or the command line
Product: [openSUSE] SUSE LINUX 10.0 Reporter: marco pedrosa <marco.pedrosa>
Component: FirefoxAssignee: Daniel Bornkessel <dbornkessel>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: x86   
OS: All   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description marco pedrosa 2005-10-11 14:25:15 UTC
although when you click on a java web start link in firefox, it recognizes it as
such, firefox does not actually launch web start be default. Browsing to the web
start executable for the system causes nothing to happen.  On the command line,
even after setting the webstart home environment variable, launching webstart
with the jnlp file url on the command line doesn't cause anything to happen.
Comment 1 Wolfgang Rosenauer 2005-10-11 18:19:26 UTC
reassign to Java folks to get information if and how this should work at all
Comment 2 Daniel Bornkessel 2005-10-27 10:10:07 UTC
Thanks for the report and sorry for the delayed answer.
There are actually two problems concerning Java Web Start:
- First of all, if you use Java 1.4, there is already the bug Bug #63780 which up to now didn't get fixed by Sun. The problem is related to the 'javaws' executable. A word-around that needs a little bit of work can be found at http://www.advogato.org/person/rmathew/diary.html?start=70
- Secondly, with Java 1.5 the binary 'javaws' works correctly for me. However, it is possible that you have to create a missing symbolic link by hand:

ln -s /etc/alternatives/javaws/javaws /usr/bin/javaws

This will be fixed.

So, the easiest to get it run now is to use Java 1.5 and -- if necessary -- set the symbolic link.
Comment 3 Daniel Bornkessel 2005-11-23 15:33:01 UTC
Fixed for java-1_4_2-sun, java-1_5_0-sun, java-1_4_2-ibm and java-1_4_2-bea.
Will close this bug as fixed ... as soon as the decision whether Blackdown will be distributed with the distribution or not, the bug will be fixed there as well.