程序包 com.alibaba.bytekit.log

类 Loggers

java.lang.Object
com.alibaba.bytekit.log.Loggers
public abstract class Loggers extends Object
Expose static methods to get a logger depending on the environment. If SL4J is on the classpath, it will be used. Otherwise, there are two possible fallbacks: Console or java.util.logging.Logger). By default, the Console fallback is used. To use the JDK loggers, set the "bytekit.logging.fallback" System property to "JDK".

One can also force the implementation by using the "useXXX" static methods: useConsoleLoggers(), useVerboseConsoleLoggers(), useJdkLoggers() and useSl4jLoggers() (which may throw an Exception if the library isn't on the classpath). Note that the system property method above is preferred, as no cleanup of the logger factory initialized at startup is attempted by the useXXX methods.

  • 字段详细资料

    • FALLBACK_PROPERTY

      public static final String FALLBACK_PROPERTY
      The system property that determines which fallback implementation to use for loggers when SLF4J isn't available. Use JDK for the JDK-backed logging and anything else for Console-based (the default).
      另请参阅:

  • 方法详细资料

    • resetLoggerFactory

      public static final void resetLoggerFactory()
      Attempt to activate the best bytekit Logger factory, by first attempting to use the SLF4J one, then falling back to either Console logging or java.util.logging.Logger). By default, the Console fallback is used. To fallback to the JDK loggers, set the "bytekit.logging.fallback" System property to "JDK".
      另请参阅:

    • useConsoleLoggers

      public static final void useConsoleLoggers()
      Force the usage of Console-based Loggers, even if SLF4J is available on the classpath. Console loggers will output ERROR and WARN levels to System.err and levels below to System.out. All levels except TRACE and DEBUG are considered enabled. TRACE and DEBUG are omitted.

      The previously active logger factory is simply replaced without any particular clean-up.

    • useVerboseConsoleLoggers

      public static final void useVerboseConsoleLoggers()
      Force the usage of Console-based Loggers, even if SLF4J is available on the classpath. Console loggers will output ERROR and WARN levels to System.err and levels below to System.out. All levels (including TRACE and DEBUG) are considered enabled.

      The previously active logger factory is simply replaced without any particular clean-up.

    • useJdkLoggers

      public static final void useJdkLoggers()
      Force the usage of JDK-based Loggers, even if SLF4J is available on the classpath.

      The previously active logger factory is simply replaced without any particular clean-up.

    • useSl4jLoggers

      public static final void useSl4jLoggers()
      Force the usage of SL4J-based Loggers, throwing an exception if SLF4J isn't available on the classpath. Prefer using resetLoggerFactory() as it will fallback in the later case.

      The previously active logger factory is simply replaced without any particular clean-up.

    • getLogger

      public static Logger getLogger(String name)
      Get a Logger.

      For a notion of how the backing implementation is chosen, see resetLoggerFactory() (or call one of the useXxxLoggers methods).

      参数:
      name - the category or logger name to use
      返回:
      a new Logger instance

    • getLogger

      public static Logger getLogger(Class<?> cls)
      Get a Logger, backed by SLF4J if present on the classpath or falling back to java.util.logging.Logger.
      参数:
      cls - the source Class to derive the logger name from.
      返回:
      a new Logger instance