Java 为什么可以';扩展log4j时,在log4j中记录方法名称和代码行
我已经扩展了log42记录器 想法: 我应该将enum传递给log方法,以便在运行时选择appender 我的界面:Java 为什么可以';扩展log4j时,在log4j中记录方法名称和代码行,java,logging,log4j,log4j2,Java,Logging,Log4j,Log4j2,我已经扩展了log42记录器 想法: 我应该将enum传递给log方法,以便在运行时选择appender 我的界面: public interface MyLoggerInterface { void info(String logMessage, MyLoggerAppenderEnum... appender); public static MyLoggerInterface getLogger(Class aClass, MyLoggerAppenderEnum... ap
public interface MyLoggerInterface {
void info(String logMessage, MyLoggerAppenderEnum... appender);
public static MyLoggerInterface getLogger(Class aClass, MyLoggerAppenderEnum... appender) {
return MyLoggerInterfaceImpl.getLogger(aClass, appender);
}
}
public class MyLoggerInterfaceImpl extends Logger implements MyLoggerInterface {
private static final String FQCN = MyLoggerInterfaceImpl.class.getName();
protected MyLoggerInterfaceImpl(LoggerContext context, String name, MessageFactory messageFactory) {
super(context, name, messageFactory);
}
public static MyLoggerInterface getLogger(Class aClass, MyLoggerAppenderEnum... appenders) {
return getLogger(aClass.getName(), appenders);
}
private static MyLoggerInterface getLogger(String name, MyLoggerAppenderEnum... appenders) {
return (MyLoggerInterfaceImpl) org.apache.logging.log4j.LogManager.getLogger(name);
}
@Override
public void info(String logMessage, MyLoggerAppenderEnum... appenders) {
this.log(FQCN, Level.INFO, null, new SimpleMessage(logMessage), null, appenders);
}
private void log(String fqcn, Level level, Marker marker, Message message, Throwable throwable, MyLoggerAppenderEnum... appenders) {
Arrays.stream(appenders)
.map(appender -> findAppenderByName(appender))
.collect(Collectors.toList())
.forEach(appender ->
appender.append(
new Log4jLogEvent(this.getName(), marker, fqcn, level, message, new ArrayList<Property>(), throwable)
)
);
}
private Appender findAppenderByName(MyLoggerAppenderEnum appenders) {
return this.getAppenders().get(appenders.name());
}
}
实施:
public interface MyLoggerInterface {
void info(String logMessage, MyLoggerAppenderEnum... appender);
public static MyLoggerInterface getLogger(Class aClass, MyLoggerAppenderEnum... appender) {
return MyLoggerInterfaceImpl.getLogger(aClass, appender);
}
}
public class MyLoggerInterfaceImpl extends Logger implements MyLoggerInterface {
private static final String FQCN = MyLoggerInterfaceImpl.class.getName();
protected MyLoggerInterfaceImpl(LoggerContext context, String name, MessageFactory messageFactory) {
super(context, name, messageFactory);
}
public static MyLoggerInterface getLogger(Class aClass, MyLoggerAppenderEnum... appenders) {
return getLogger(aClass.getName(), appenders);
}
private static MyLoggerInterface getLogger(String name, MyLoggerAppenderEnum... appenders) {
return (MyLoggerInterfaceImpl) org.apache.logging.log4j.LogManager.getLogger(name);
}
@Override
public void info(String logMessage, MyLoggerAppenderEnum... appenders) {
this.log(FQCN, Level.INFO, null, new SimpleMessage(logMessage), null, appenders);
}
private void log(String fqcn, Level level, Marker marker, Message message, Throwable throwable, MyLoggerAppenderEnum... appenders) {
Arrays.stream(appenders)
.map(appender -> findAppenderByName(appender))
.collect(Collectors.toList())
.forEach(appender ->
appender.append(
new Log4jLogEvent(this.getName(), marker, fqcn, level, message, new ArrayList<Property>(), throwable)
)
);
}
private Appender findAppenderByName(MyLoggerAppenderEnum appenders) {
return this.getAppenders().get(appenders.name());
}
}
上下文选择器:
public class MyLoggerContextSelector implements ContextSelector {
private final LoggerContext CONTEXT = new MyLoggerContext("MyLoggerContext");
public LoggerContext getContext(String fqcn, ClassLoader loader, boolean currentContext) {
return CONTEXT;
}
public LoggerContext getContext(String fqcn, ClassLoader loader, boolean currentContext, URI configLocation) {
return CONTEXT;
}
public List<LoggerContext> getLoggerContexts() {
return Arrays.asList(CONTEXT);
}
public void removeContext(LoggerContext context) {
}
}
和经理:
public class MyLoggerManager {
public static void initialize(String configURL) {
try {
System.setProperty("log4j2.loggerContextFactory", "ge.test.core.logging.MyLoggerLog4jContextFactory");
System.setProperty("Log4jLogEventFactory", "org.apache.logging.log4j.core.impl.DefaultLogEventFactory");
Configurator.initialize(null, configURL);
} catch (Exception ex ) {
System.err.println("Cannot initialize Log4J using configuration url:" + configURL);
}
}
}
酷!一切都很好和用法:
MyLoggerManager.initialize("Log4j2.xml");
MyLoggerInterface logger = MyLoggerInterface.getLogger(AppLauncher.class);
logger.info("test", MyLoggerAppenderEnum.Console);
但问题是,若使用扩展自定义记录器,则无法记录方法名称和行。布局正确如果我不使用扩展自定义记录器,也会记录方法名称和行
<Configuration status="WARN">
<Appenders>
<Console name="Console" target="SYSTEM_OUT">
<PatternLayout pattern="%d{HH:mm:ss.SSS} [%t] %-5level %logger{36} %method:%line - %msg%n"/>
</Console>
...
</Appenders>
<Loggers>
...
<Logger name="Console" level="trace" additivity="false">
<appender-ref ref="Console" level="trace"/>
</Logger>
...
<Root level="error">
...
<AppenderRef ref="Console"/>
</Root>
</Loggers>
</Configuration>
我的代码在这里
我使用log4j 2.9.1
我认为这里有两个问题:
手册页面有三个示例,但是(“如何动态写入单独的日志文件?”)可能非常适合您的要求。该示例使用
ThreadContext
映射来控制后续事件(在当前线程中)记录到哪个日志文件。我认为这里有两个问题:
手册页面有三个示例,但是(“如何动态写入单独的日志文件?”)可能非常适合您的要求。该示例使用
ThreadContext
映射来控制后续事件(在当前线程中)记录到哪个日志文件。当我阅读您的问题时,感觉就像是一个问题。有很多方法可以在运行时使用现有的log4j2功能选择appender,例如,如果这是您扩展log4j2的唯一原因,我建议您进行更多的研究,并尽可能尝试使用提供的功能。我想传递我的enum并在运行时选择appender。我没有看到任何这样的例子。我更新了我的答案。当我读到你的问题时,感觉像是一个错误。有很多方法可以在运行时使用现有的log4j2功能选择appender,例如,如果这是您扩展log4j2的唯一原因,我建议您进行更多的研究,并尽可能尝试使用提供的功能。我想传递我的enum并在运行时选择appender。我没有看到这样的例子。我更新了我的答案。