|
Quick Lists
|
|
Bug ID:
|
4429811
|
|
Votes
|
0
|
|
Synopsis
|
Application launched by JWS 1.0.1 has no Swing Display at all (B57)
|
|
Category
|
javawebstart:app_mgr
|
|
Reported Against
|
merlin-beta
|
|
Release Fixed
|
1.0.1
|
|
State
|
11-Closed,
Verified,
bug
|
|
Priority:
|
1-Very High
|
|
Related Bugs
|
4421552
,
4423128
,
4429816
,
4434688
,
4711515
|
|
Submit Date
|
24-MAR-2001
|
|
Description
|
Test case link:
http://comanche/jawstest/merlin/hellojaws/
Step to reproduce (On Window):
- Install Merlin B57.
- Due to another bug, after installing Merlin B57, you have to remove JWS
1.0.1, which was bundled inside Merlin. (By default, that JWS 1.0.1 was
installed into "C:\Program Files\JavaSoft\Java Web Start", that caused
another bug.)
- From /usr/local/java/javaws1.0.1fcs/bundles, get
javaws-1_0_1-win-us.exe
Install this one into a dir which does not contain ' ', such as C:\JWS101.
- Restart your browser, from above page, click the first jnlp link. You will
see the application is running. But there is nothing displayed.
xxxxx@xxxxx 2001-03-23
|
|
Work Around
|
N/A
|
|
Evaluation
|
When I modified this code to do an invokeLater, the Runnable was never run. This may be related to java web start spanning its own AppContext and thus its own EventQueue. I'm reassigning to awt for further investigation.
xxxxx@xxxxx 2001-03-26
Commit to fix in Merlin-beta (blocks java webstart).
xxxxx@xxxxx 2001-03-27
This is possibly a duplicate of 4429816.
xxxxx@xxxxx 2001-03-29
The source code shown at..
http://comanche/jawstest/merlin/hellojaws/code.html#file4 (src/hellojaws.java)
is not consistent with the actual behavior of the application in jar/hellojaws.jar. I need the actual source code of the provided application to investigate this bug further. Please attach the current hellojaws.java and the hellojaws.jar to this bug.
xxxxx@xxxxx 2001-04-03
Updated the code.html for new test source.
The workspace could be found:
/net/sqesvr/deployment2/yuwang/ws/tests/jaws/merlin/hellojaws
xxxxx@xxxxx 2001-04-03
This looks like a WebStart problem. Notice in the comments that the AppContext in the application has two AWT-EventQueue threads. There should only be one.
xxxxx@xxxxx 2001-04-05
The above problem is caused by a change to EventQueue.java. Prior to Merlin EventQueue.java created the AWT-EventQueue thread in the constructor, now it is created on the posting of the first event. This causes trouble for WebStart. I believe this is related to the fixes for 4271416 and 4030718. See the comments section for the code snippet WebStart uses to create an AppContext
xxxxx@xxxxx 2001-04-06
This has been fixed by running application in it's own thread group.
xxxxx@xxxxx 2001-04-13
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |