abstract class NamedLoggerBase extends java.lang.Object implements Logger, java.io.Serializable
readResolve()
Modifier and Type | Field and Description |
---|---|
protected java.lang.String |
name |
private static long |
serialVersionUID |
ROOT_LOGGER_NAME
Constructor and Description |
---|
NamedLoggerBase() |
Modifier and Type | Method and Description |
---|---|
java.lang.String |
getName()
Return the name of this
Logger instance. |
protected java.lang.Object |
readResolve()
Replace this instance with a homonymous (same name) logger returned
by LoggerFactory.
|
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
debug, debug, debug, debug, debug, debug, debug, debug, debug, debug, error, error, error, error, error, error, error, error, error, error, info, info, info, info, info, info, info, info, info, info, isDebugEnabled, isDebugEnabled, isErrorEnabled, isErrorEnabled, isInfoEnabled, isInfoEnabled, isTraceEnabled, isTraceEnabled, isWarnEnabled, isWarnEnabled, trace, trace, trace, trace, trace, trace, trace, trace, trace, trace, warn, warn, warn, warn, warn, warn, warn, warn, warn, warn
private static final long serialVersionUID
protected java.lang.String name
public java.lang.String getName()
Logger
Logger
instance.protected java.lang.Object readResolve() throws java.io.ObjectStreamException
This approach will work well if the desired ILoggerFactory is the one references by LoggerFactory. However, if the user manages its logger hierarchy through a different (non-static) mechanism, e.g. dependency injection, then this approach would be mostly counterproductive.
java.io.ObjectStreamException