| com.google.gwt.core.ext.TreeLogger
All known Subclasses: com.google.gwt.dev.util.log.AbstractTreeLogger, com.google.gwt.dev.util.log.ThreadLocalTreeLoggerProxy,
| TreeLogger | | public interface TreeLogger (Code) | | An interface used to log messages in deferred binding generators.
|
| Field Summary | |
| Type | ALL
Logs everything -- quite a bit of stuff. | | Type | DEBUG
Logs detailed information that could be useful during debugging. | | Type | ERROR
Logs an error. | | Type | INFO
Logs information. | | TreeLogger | NULL
A valid logger that ignores all messages. | | Type | SPAM
Logs extremely verbose and detailed information that is typically useful
only to product implementors. | | Type | TRACE
Logs information related to lower-level operation. | | Type | WARN
Logs a warning. |
| ALL | | Type ALL(Code) | | Logs everything -- quite a bit of stuff.
|
| DEBUG | | Type DEBUG(Code) | | Logs detailed information that could be useful during debugging.
|
| ERROR | | Type ERROR(Code) | | Logs an error.
|
| INFO | | Type INFO(Code) | | Logs information.
|
| NULL | | TreeLogger NULL(Code) | | A valid logger that ignores all messages. Occasionally useful when calling
methods that require a logger parameter.
|
| SPAM | | Type SPAM(Code) | | Logs extremely verbose and detailed information that is typically useful
only to product implementors.
|
| TRACE | | Type TRACE(Code) | | Logs information related to lower-level operation.
|
| WARN | | Type WARN(Code) | | Logs a warning.
|
| branch | | TreeLogger branch(TreeLogger.Type type, String msg, Throwable caught)(Code) | | Produces a branched logger, which can be used to write messages that are
logically grouped together underneath the current logger. The details of
how/if the resulting messages are displayed is implementation-dependent.
The log message supplied when branching serves two purposes. First, the
message should be considered a heading for all the child messages below it.
Second, the type of the message provides a hint as to the
importance of the children below it. As an optimization, an implementation
could return a "no-op" logger if messages of the specified type weren't
being logged, which the implication being that all nested log messages were
no more important than the level of their branch parent.
As an example of how hierarchical logging can be used, a branched logger in
a GUI could write log message as child items of a parent node in a tree
control. If logging to streams, such as a text console, the branched logger
could prefix each entry with a unique string and indent its text so that it
could be sorted later to reconstruct a proper hierarchy.
Parameters:
type -
Parameters:
msg - An optional message to log, which can be null ifonly an exception is being logged
Parameters:
caught - An optional exception to log, which can be nullif only a message is being logged an instance of TreeLogger representing the new branch ofthe log. May be the same instance on which this method is called |
| isLoggable | | boolean isLoggable(TreeLogger.Type type)(Code) | | Determines whether or not a log entry of the specified type would actually
be logged. Caller use this method to avoid constructing log messages that
would be thrown away.
|
| log | | void log(TreeLogger.Type type, String msg, Throwable caught)(Code) | | Logs a message and/or an exception. It is also legal to call this method
using null arguments for both msg and
caught, in which case the log event can be ignored.
Parameters:
type -
Parameters:
msg - An optional message to log, which can be null ifonly an exception is being logged
Parameters:
caught - An optional exception to log, which can be nullif only a message is being logged |
|
|