Following properties related to tracing and logging feature introduced in tiger is not working as advertised:
deployment.javaws.traceFileName
deployment.javaws.logFileName
deployment.javapi.trace.filename
deployment.javapi.log.filename

When these properties are set along with "deployment.trace" and "deployment.log", both set to true, then log and trace files for both Plug-in and JAWS should get generated with the filenames specified against these properties. But that's not happening in reality.

Steps to reproduce:
------------------
1) Logging and tracing under default log location
Create deployment.properties file with following properties:
deployment.trace=true
deployment.javaws.traceFileName=test_jaws_trace
deployment.javaws.logFileName=test_jaws_log
deployment.javapi.trace.filename=test_jpi_trace
deployment.javapi.log.filename=test_jpi_log
deployment.log=true

Launch following applet/JAWS application
http://sqeweb.sfbay.sun.com/deployment2/jitu/plug-bug/applet_communication/static_var/test1/applet_frame.html

http://nicole1.sfbay.sun.com:8080/JavawsMustangIntegTest/hellojaws/BAT.jnlp

  Excepted behavior:
  Both applet and JAWS applets should run successfully with trace and log files with the above mentioned names getting created inside the default log location i.e. under <user_dep_home>/log

  Actual Behavior:
  JAWS:
   - Trace and log files are not getting created at all both with 1.5 and 1.6
   - On invokation of JAWS application or applet value for property "deployment.javaws.traceFileName" is getting assigned value of deployment.javaws.logFileName i.e. deployment.properties will have following entry after invokation of JAWS application or applet
deployment.javaws.traceFileName=test_jaws_log (originally set to "test_jaws_trace")
deployment.javaws.logFileName=test_jaws_log

Applets:
 - Applet fails to launch with 1.5 by throwing following exception :

basic: Registered modality listener
liveconnect: Invoking JS method: document
basic: Registered modality listener
liveconnect: Invoking JS method: document
liveconnect: Invoking JS method: URL
liveconnect: Invoking JS method: URL
basic: Referencing classloader: sun.plugin.ClassLoaderInfo@dd5b, refcount=1
basic: Referencing classloader: sun.plugin.ClassLoaderInfo@dd5b, refcount=2
Exception in thread "Thread-3" java.lang.ClassCastException: sun.net.ProgressMonitor
at sun.plugin.util.GrayBoxPainter.beginPainting(Unknown Source)
at sun.plugin.AppletViewer.initApplet(Unknown Source)
at sun.plugin.AppletViewer.appletInit(Unknown Source)
at sun.plugin.viewer.LifeCycleManager.initAppletPanel(Unknown Source)
at sun.plugin.viewer.IExplorerPluginObject$Initer.run(Unknown Source)
Exception in thread "Thread-2" java.lang.ClassCastException: sun.net.ProgressMonitor
at sun.plugin.util.GrayBoxPainter.beginPainting(Unknown Source)
at sun.plugin.AppletViewer.initApplet(Unknown Source)
at sun.plugin.AppletViewer.appletInit(Unknown Source)
at sun.plugin.viewer.LifeCycleManager.initAppletPanel(Unknown Source)
at sun.plugin.viewer.IExplorerPluginObject$Initer.run(Unknown Source)


- With 1.6 applets is getting launched successfully but empty trace and log files are getting generated with original names.
- With 1.6 if applet is invoked again with JAVA Console already running then trace and log files are getting generated properly but with original names


2) Logging and tracing under user defined log location:
------------------------------------------------------
Specify following inside the deployment properties file:
deployment.trace=true
deployment.javaws.traceFileName=C\:\\<some_existing_location>\\test_jaws_trace
deployment.javaws.logFileName=C\:\\<some_existing_location>\\test_jaws_log
deployment.javapi.trace.filename=C\:\\<some_existing_location>\\test_jpi_trace
deployment.javapi.log.filename=C\:\\<some_existing_location>\\test_jpi_log
deployment.log=true

Say <some_existing_location> is set to C:\temp

JAWS:
   - Trace file is not getting created at all both with 1.5 and 1.6 while log file is there
   - On invokation of JAWS application value for property "deployment.javaws.traceFileName" is getting assigned value of deployment.javaws.logFileName i.e. deployment.properties will have following entry after invokation of JAWS application or applet
deployment.javaws.traceFileName=C\:\\temp\\jitu_jaws_log (originally set to "C\:\\temp\\jitu_jaws_trace")
deployment.javaws.logFileName=C\:\\temp\\jitu_jaws_log


Applets:
 Launched successfully both with 1.5 and 1.6
With 1.5 empty trace and log files with the name of test_jpi_log.log and test_jpi_trace.trace are getting created under C:\temp. Trace and log is getting dumped if Java console is invoked. Also the lock file test_jpi_log.lck is not getting removed on quitting the browser
With 1.6 no trace and log files are getting created inside C:\temp but they are getting created inside the Default location(user_der_home/log) with default names