net.yura.mobile.logging

Class Logger

java.lang.Object

net.yura.mobile.logging.Logger

public class Logger
extends java.lang.Object

Author:

Orens

Field Summary

Fields

Modifier and Type	Field and Description
static int	DEBUG
static int	ERROR
static int	FATAL can not log at this level, is used to turn off logging
static int	INFO
static int	WARN

Constructor Summary

Constructors

Modifier	Constructor and Description
protected	Logger()

Method Summary

Modifier and Type	Method and Description
static void	debug(java.lang.String message) Debug logging is the most verbose and can be used for any type of logging.
static void	debug(java.lang.String error, java.lang.Throwable exception) Debug logging is the most verbose and can be used for any type of logging.
static void	dumpStack() same as the Java SE method with the same name
static void	error(java.lang.String message) Error logging should be used for serious errors which should be reported even on a release build.
static void	error(java.lang.String error, java.lang.Throwable throwable) Error logging should be used for serious errors which should be reported even on a release build.
static int	getLevel()
static void	info(java.lang.String message) Info logging should be used for information that may prove useful for any developer.
static void	info(java.lang.String error, java.lang.Throwable exception) Info logging should be used for information that may prove useful for any developer.
protected void	log(java.lang.String message, int level)
protected void	log(java.lang.String error, java.lang.Throwable throwable, int level)
static void	setLevel(int level)
static void	setLogger(Logger logger)
protected java.lang.String	toString(int level)
static void	warn(boolean assertion) Warn logging should be used for any errors or bugs.
static void	warn(java.lang.String message) Warn logging should be used for any errors or bugs.
static void	warn(java.lang.String error, java.lang.Throwable exception) Warn logging should be used for any errors or bugs.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

DEBUG

public static final int DEBUG

See Also:

Level.FINE, Constant Field Values

INFO

public static final int INFO

See Also:

Level.INFO, Constant Field Values

WARN

public static final int WARN

See Also:

Level.WARNING, Constant Field Values

ERROR

public static final int ERROR

See Also:

Level.SEVERE, Constant Field Values

FATAL

public static final int FATAL

can not log at this level, is used to turn off logging

See Also:

Level.OFF, Constant Field Values

Constructor Detail

Logger

protected Logger()

Method Detail

setLogger

public static void setLogger(Logger logger)

setLevel

public static void setLevel(int level)

See Also:

Logger.setLevel(java.util.logging.Level)

getLevel

public static int getLevel()

See Also:

Logger.getLevel()

debug

public static void debug(java.lang.String message)

Debug logging is the most verbose and can be used for any type of logging. Developers will only need to see this info when debugging a problem and should work at the info level most of the time to avoid all the output. Expected exceptions can be reported on the debug level

debug

public static void debug(java.lang.String error,
                         java.lang.Throwable exception)

Debug logging is the most verbose and can be used for any type of logging. Developers will only need to see this info when debugging a problem and should work at the info level most of the time to avoid all the output. Expected exceptions can be reported on the debug level

info

public static void info(java.lang.String message)

Info logging should be used for information that may prove useful for any developer. Logging related to debugging a specific issue or with lots of output should use the debug level. Unexpected exceptions without implications can be reported on the info level.

info

public static void info(java.lang.String error,
                        java.lang.Throwable exception)

Info logging should be used for information that may prove useful for any developer. Logging related to debugging a specific issue or with lots of output should use the debug level. Unexpected exceptions without implications can be reported on the info level.

warn

public static void warn(java.lang.String message)

Warn logging should be used for any errors or bugs. Unexpected exceptions with implications and errors can be reported on the warn level.

warn

public static void warn(java.lang.String error,
                        java.lang.Throwable exception)

Warn logging should be used for any errors or bugs. Unexpected exceptions with implications and errors can be reported on the warn level. Warn logging can also and should be used for assertions.

warn

public static void warn(boolean assertion)

Warn logging should be used for any errors or bugs. Unexpected exceptions with implications and errors can be reported on the warn level. Warn logging can also and should be used for assertions.

error

public static void error(java.lang.String message)

Error logging should be used for serious errors which should be reported even on a release build. Throwable try catch blocks surrounding code entry points should report on the error level.

error

public static void error(java.lang.String error,
                         java.lang.Throwable throwable)

Error logging should be used for serious errors which should be reported even on a release build. Throwable try catch blocks surrounding code entry points should report on the error level.

dumpStack

public static void dumpStack()

same as the Java SE method with the same name

See Also:

Thread.dumpStack()

toString

protected java.lang.String toString(int level)

log

protected void log(java.lang.String message,
                   int level)

log

protected void log(java.lang.String error,
                   java.lang.Throwable throwable,
                   int level)