Skip to content

logging.md

Latest commit

 

History

History
50 lines (28 loc) · 1.77 KB

logging.md

File metadata and controls

50 lines (28 loc) · 1.77 KB

Logging

Log4j2 is my preferred logging library but according to this ticket LOG4J2-2649, this library has not yet supported native compilation. The tracking ticket in Github is issue 1539.

In the mean time, the next available logging library is Logback and is what this application is configured with.

Maven Dependency

We only have to add the dependency on logback-classic library and it will bring in slf4j-api dependency.

<dependency>
    <groupId>ch.qos.logback</groupId>
    <artifactId>logback-classic</artifactId>
    <version>${logback-classic.version}</version>
</dependency>

Configuration

We can customize logging configuration through logback.xml file. This file can be placed under src/main/resouces directory and we will make it available to native-image when building the binary.

See Resources for details.

Initialization

The com.demo.Main is the application's entry point. In order to instruct Vert.x to use Logback as the logging library, in this class we have to add a few configurations.

To let Vert.x know to use Logback, we set the vertx.logger-delegate-factory-class-name system property with SLF4JLogDelegateFactory.

To tell Vert.x where to find logback.xml file, we set the logback.configurationFile system property to the absolute path to this file.

After all that, we then create an instance of org.slf4j.Logger using org.slf4j.LoggerFactory's static method.

In all other classes, we continue the usual way of creating Logger instance.

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
...

private static Logger logger = LoggerFactory.getLogger(MainVerticle.class);