Customer is requesting native debugging flags to debug java web start
(JWS) start up issues, for jdk 1.4.2_x and beyond.

One can use deployment.properties file to turn on logging:
deployment.javaws.showConsole=true
deployment.javaws.logToFile=true
deployment.javaws.logFileName=C\:\\javaws142.log
but this only helps if java is successfully invoked, and will not help
if java web start fails at start up itself. We did get output when
using these properties, only when the application was successfully
started.

Unfortunately, its the same case when using commonly unknown debugging
option of placing the .javawsrc file, with all tracing enabled, in the
start-in location for the java webstart application. We saw output
being generated only when the webstart application was successfully
launched (i.e., JVM being invoked). We did not get any needed debugging
output when the java webstart application failed to start.

We had a scenario where java webstart was not starting, when being invoked
using a desktop short cut "<install-dir>/javaws.exe <install-dir>myapp.jnlp",
on Win XP system, which was a "locked-down" system.

By trial and error it was found out that this was due to some properties'
setup in a 3rd party software "Altiris eXpress Metering Agent".
It would have helped us immensely, if there are native debugging flags,
to debug java webstart start up issues, that are not caught by the
java level properties set in "deployment.properties" file, or that are
set in .javawsrc file.

This Request For Future Enhancement (RFE) is to request for native
debugging flags, to debug java webstart (JWS) start up issues,
for jdk 1.4.2_x and beyond.

###@###.### 2005-1-01 00:01:21 GMT