open class JULLogDelegate : LogDelegate
A io.vertx.core.spi.logging.LogDelegate which delegates to java.util.logging |
|
open class JULLogDelegateFactory : LogDelegateFactory
A io.vertx.core.spi.logging.LogDelegateFactory which creates JULLogDelegate instances. |
|
open class Log4j2LogDelegate : LogDelegate
A LogDelegate which delegates to Apache Log4j 2 |
|
open class Log4j2LogDelegateFactory : LogDelegateFactory
A LogDelegateFactory which creates Log4j2LogDelegate instances. |
|
open class Log4jLogDelegate : LogDelegate
A io.vertx.core.spi.logging.LogDelegate which delegates to Apache Log4j |
|
open class Log4jLogDelegateFactory : LogDelegateFactory
A io.vertx.core.spi.logging.LogDelegateFactory which creates Log4jLogDelegate instances. |
|
open class Logger
This class allows us to isolate all our logging dependencies in one place. It also allows us to have zero runtime 3rd party logging jar dependencies, since we default to JUL by default. By default logging will occur using JUL (Java-Util-Logging). The logging configuration file (logging.properties) used by JUL will taken from the default logging.properties in the JDK installation if no If you would prefer to use Log4J or SLF4J instead of JUL then you can set a system property called Keep in mind that logging backends use different formats to represent replaceable tokens in parameterized messages. As a consequence, if you rely on parameterized logging methods, you won't be able to switch backends without changing your code. |
|
open class LoggerFactory |
|
open class SLF4JLogDelegate : LogDelegate |
|
open class SLF4JLogDelegateFactory : LogDelegateFactory |
|
open class VertxLoggerFormatter : Formatter |