java.lang.Object
konspire.common.log.AbstractLoggingMechanism
konspire.common.log.AbstractFileLoggingMechanism
konspire.common.log.UniqueFileLoggingMechanism
- Direct Known Subclasses:
- UniqueDatedFileLoggingMechanism
- public class UniqueFileLoggingMechanism
- extends AbstractFileLoggingMechanism
This logging mechanism is the simplest implementation of a file logging
mechanism. It is designed to have one log file per log, with the name
of the log as part of the file name. It doesn't do anything fancy like
rolling over to a new file when a date changes, it appends all messages
to the same file name if already present.
- Version:
- $Revision: 1.3 $
| Methods inherited from class konspire.common.log.AbstractLoggingMechanism |
closeForLog, compactCurrentDate, currentDate, currentTime, getLoggingMechanismForString, getName, hasDateRolledOver, isDatedLog, loggingPrefix, logString, notifyLogClosed, notifyLoggingLevelChange, notifyLogOpened, openForLog, rollLogOver |
UniqueFileLoggingMechanism
public UniqueFileLoggingMechanism()
getInstance
public static AbstractLoggingMechanism getInstance()
isSharedLog
protected boolean isSharedLog()
- Description copied from class:
AbstractLoggingMechanism
- Mechanisms can be shared or unique. Shared mechanisms
require the log name to be in every log entry (so you
can distinguish between the log entries). Unique
mechanisms name themselves uniquely (for example, have
the log name in their file name) so they do not
have to put the name of the log in their log entry.
The default is shared (true).
- Overrides:
isSharedLog in class AbstractLoggingMechanism