diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/logger/uiLoggerAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/logger/uiLoggerAPI.html index f41f445d999..346a58651ea 100755 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/logger/uiLoggerAPI.html +++ b/rse/doc/org.eclipse.rse.doc.isv/guide/api/logger/uiLoggerAPI.html @@ -3,72 +3,14 @@ - + RSE Logger API - +

RSE Logger API

-

To use the RSE logging framework, you must first decide if you want your own log file, -or want to use the common RSE log file. -

- -

Using Your Own Log File

-

-The log file support is encapsulated in the org.eclipse.rse.logging package, which -defines the primary org.eclipse.rse.logging.Logger class that manages the log file. -This log file support offers the ability to log the following types of log messages:

- - -

To define your own logging file, in your plugin class:

-
    -
  1. Define a static variable to hold the Logger instance, as in:
    -protected static Logger log = null; -
  2. Instantiate the Logger object, in your plugin class constructor, as in:
    - if (log == null) log = LoggerFactory.getLogger(this); -
  3. For convenience, offer fastpaths to the logXXX methods in your Logger instance: -
    -    public static void logInfo(String message)
-    {
-    	log.logInfo(message);
-    }
-    public static void logWarning(String message)
-    {
-    	log.logWarning(message);
-    }
-    public static void logError(String message)
-    {
-    	log.logError(message, null);
-    }
-    public static void logError(String message, Throwable exception)
-    {
-    	log.logError(message, exception);
-    }
-    public static void logDebugMessage(String prefix, String message)
-    {		
-     log.logDebugMessage(prefix, message);
-    }		
-
    -
  4. In the shutdown method of your plugin class, close the log file: -LoggerFactory.freeLogger(this); -
-

Typically your code will write a healthy number of messages to the log file, to help you determine -what went wrong in an error situation in production. However, since this can result in a large number of -messages in the log file, it is recommended that you offer the user's a preference page in which they -can specify the types of messages to record in the log file, which should default to error messages only. -In the event of a problem, they can then turn on a more verbose logging option and re-produce the problem, -sending the log file to you for additional information. For example, for the Remote System Explorer, this -preference page is supplied:

-

- -

Using The Common RSE Log File

-

To log your messages to the common RSE log file in .metadata\plugins\org.eclipse.rse.ui, +

To log your messages to the workbench log file in .metadata\.log, either base your plugin class on the org.eclipse.rse.ui.SystemBasePlugin class and use the inherited logging methods, or instead of instantiating your own Logging object, re-use the RSE-supplied logging object by calling getDefault().getLog() in the org.eclipse.rse.ui.RSEUIPlugin diff --git a/rse/doc/org.eclipse.rse.doc.isv/guide/api/uiAPI.html b/rse/doc/org.eclipse.rse.doc.isv/guide/api/uiAPI.html index f73c7fb320e..42e409da390 100755 --- a/rse/doc/org.eclipse.rse.doc.isv/guide/api/uiAPI.html +++ b/rse/doc/org.eclipse.rse.doc.isv/guide/api/uiAPI.html @@ -34,13 +34,6 @@ or an image descriptor. methods of your own.

-

Logging

-

The Remote System Explorer comes with special support for logging information to a log file, -for the purpose of problem determination for servicing your plugin. The log file support allows -you to either log your messages to the common RSE log file in the .metadata\plugins\org.eclipse.rse.core -folder, or to define your own log file in your plugin metadata folder, if desired. -

-

Messages

The Java property file for messages is not very rich, as it offers only the ability to define a single message string. Throughout the RSE perspective you will notice that the messages are richer