United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-6297222 : Silent startup for applications that run on system startup

Details
Type:
Enhancement
Submit Date:
2005-07-15
Status:
Closed
Updated Date:
2010-12-07
Project Name:
JDK
Resolved Date:
2010-12-07
Component:
deploy
OS:
windows_xp
Sub-Component:
webstart
CPU:
x86
Priority:
P4
Resolution:
Won't Fix
Affected Versions:
5.0
Fixed Versions:
7

Related Reports

Sub Tasks

Description
A DESCRIPTION OF THE REQUEST :
For Webstart applications that get launched on system startup it is annoying to the end-user to have to see a splash screen. This is further aggravated by the fact that the system loads applications slower on startup so the splash screen will likely remain visible far longer than normal.

The JNLP descriptor should be able to specify that the application does not wish to display any splash screen on startup.

A separate descriptor tag should also be added which will allow the "online" applications to update without showing any UI either, unless an update failure occured.

The expected behavior is for the application to run on startup, update itself and begin running, all without any visible UI.

For example, in my application's case, I simply want it to add itself to the system tray on startup.

JUSTIFICATION :
Current behavior annoys end-users
###@###.### 2005-07-15 07:27:37 GMT

                                    

Comments
EVALUATION

several RFE's here:
1.) jnlp spec change to allow specification of no splash screen. (future enhancement)
2.) jnlp element to allow shortcut to be created with app to run with "-quiet" mode (will not likely implement, but worth considering in larger review of possible future functionality)
3.) seperate default behavior for shortcut run on startup, than run otherwise. (this is a smaller part of a more general enhancement to allow setting up javaws app to run as a service on windows, or to run at all on startup on unix)

###@###.### 2005-07-15 14:40:36 GMT
                                     
2005-07-15
EVALUATION

1.) the default splash can be avoided by specifying a progress-class attribute to the application-desc (or applet-desc).  If no jar is specified as download="progress", this progress-class attribute will have no other effect.

2.) avoiding the download dialog can be accomplished now using the custom progress feature, and implementing and dummy set of progress listeners.

3.) avoiding the download dialog only sometimes can also be accomplished using intelegent custom progress implementation.

Therefor the functionality requested already exists, and this will be closed as "will not fix"
                                     
2010-12-07



Hardware and Software, Engineered to Work Together