nl.demon.shadowland.freedumbytes.java.util.logging.manager.Slf4jLogManager Maven / Gradle / Ivy

Go to download
package nl.demon.shadowland.freedumbytes.java.util.logging.manager;


import java.util.logging.LogManager;
import java.util.logging.Logger;

import lombok.extern.slf4j.Slf4j;


/**
 * Custom {@code LogManager} for {@code java.util.logging} that doesn't require {@code SLF4JBridgeHandler} and uses {@link Slf4jLoggerWrapper#isLoggable} thus removing the performance issue of the bridge handler.
 *
 * 
 * At startup the {@code LogManager} class is located using the {@code java.util.logging.manager} system property. Thus to activate this custom one use the following command line option
 * {@code -Djava.util.logging.manager=nl.demon.shadowland.freedumbytes.java.util.logging.manager.Slf4jLogManager}.
 * 
 *
 * @see Bridging legacy APIs
 * @see How to make Jersey to use SLF4J instead of JUL?
 * @see Eclipse EE4J Jersey logging
 * @see Apache CXF logging
 */
@Slf4j
public class Slf4jLogManager extends LogManager
{
  public static boolean isInstalled()
  {
    boolean installed = (LogManager.getLogManager() instanceof Slf4jLogManager);

    log.info("Slf4jLogManager is {}installed.", (installed ? "" : "NOT "));

    return installed;
  }


  @Override
  public boolean addLogger(Logger logger)
  {
    boolean addedLogger;

    if (needsWrapping(logger))
    {
      super.addLogger(new Slf4jLoggerWrapper(logger));

      addedLogger = false;
    }
    else
    {
      addedLogger = super.addLogger(logger);
    }

    return addedLogger;
  }


  private static boolean needsWrapping(Logger logger)
  {
    return !(logger instanceof Slf4jLoggerWrapper);
  }
}