Browse Prior Art Database

System and Method For Enabling Applet Debug Using Server Trace Settings Disclosure Number: IPCOM000199679D
Publication Date: 2010-Sep-14
Document File: 1 page(s) / 38K

Publishing Venue

The Prior Art Database


The problem: applets can be debugged by having the applet print debug statements to System.out which will show up in the browser java console. But once applet code is deployed to the field, you don't necessarily want it always printing debug statements to the console. Some common place solutions are to temporarily use an applet jar file with the debug statements "compiled back in" .. or temporarily change an applet parameter on an HTML page to tell the applet to print the debug statements. But these methods can be clumsy at best, especially when you are trying to communicate the procedure to service personnel possibly in another time zone who may have a different primary language than you do.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 88% of the total text.

Page 1 of 1

System and Method For Enabling Applet Debug Using Server Trace Settings

How it works: The applet one wants to debug is more than likely associated with a particular function or task on the system it is delivered from. If the system itself allows for tracing to be enabled/disabled for particular functions/tasks, then you can do the following:
(1) Have the HTML that delivers the applet be dynamically generated to the extent an applet parameter that determines the applet debug level can be set by the system delivering the HTML.
(2) In the code that dynamically generates the applet HTML, the system trace level can be checked for the function/task the applet is associated with. If that particular task is being traced specifically (as opposed to a general trace where ALL tasks are being traced), then based on the level of the tracing for that task, a different value for the applet debug level can be generated into the HTML that delivers the applet.
(3) the applet itself can check this debug parameter and based on its value, either not print debug statements, or print various levels of debug statements.

     Then to enable the applet debug, on the system the task tracing would be enabled for that specific task at some level. Then when a browser calls for the applet to be delivered to the browser, the code that is delivering the applet HTML can set the applet debug parameter accordingly so that when the applet arrives at the browser and runs, it can check the debug parameter and...