本文整理了Java中org.jboss.logmanager.Logger.detach()
方法的一些代码示例,展示了Logger.detach()
的具体用法。这些代码示例主要来源于Github
/Stackoverflow
/Maven
等平台,是从一些精选项目中提取出来的代码,具有较强的参考意义,能在一定程度帮忙到你。Logger.detach()
方法的具体详情如下:
包路径:org.jboss.logmanager.Logger
类名称:Logger
方法名:detach
[英]Remove an attachment.
[中]
代码示例来源:origin: org.jboss.logmanager/log4j-jboss-logmanager
@Override
public LoggerNode run() {
return lmLogger.detach(LOGGER_NODE_KEY);
}
});
代码示例来源:origin: org.jboss.logmanager/log4j-jboss-logmanager
loggerNode = lmLogger.detach(LOGGER_NODE_KEY);
} else {
loggerNode = AccessController.doPrivileged(new PrivilegedAction<LoggerNode>() {
代码示例来源:origin: wildfly/wildfly-core
private static void clearLogContext() {
// Remove the configurator and clear the log context
final Configurator configurator = EMBEDDED_LOG_CONTEXT.getLogger("").detach(Configurator.ATTACHMENT_KEY);
// If this was a PropertyConfigurator we can use the LogContextConfiguration API to tear down the LogContext
if (configurator instanceof PropertyConfigurator) {
final LogContextConfiguration logContextConfiguration = ((PropertyConfigurator) configurator).getLogContextConfiguration();
clearLogContext(logContextConfiguration);
} else if (configurator instanceof LogContextConfiguration) {
clearLogContext((LogContextConfiguration) configurator);
} else {
// Remove all the handlers and close them as well as reset the loggers
final List<String> loggerNames = Collections.list(EMBEDDED_LOG_CONTEXT.getLoggerNames());
for (String name : loggerNames) {
final Logger logger = EMBEDDED_LOG_CONTEXT.getLoggerIfExists(name);
if (logger != null) {
final Handler[] handlers = logger.clearHandlers();
if (handlers != null) {
for (Handler handler : handlers) {
handler.close();
}
}
logger.setFilter(null);
logger.setUseParentFilters(false);
logger.setUseParentHandlers(true);
logger.setLevel(Level.INFO);
}
}
}
}
代码示例来源:origin: org.wildfly.core/wildfly-logging
private static void clearLogContext() {
// Remove the configurator and clear the log context
final Configurator configurator = EMBEDDED_LOG_CONTEXT.getLogger("").detach(Configurator.ATTACHMENT_KEY);
// If this was a PropertyConfigurator we can use the LogContextConfiguration API to tear down the LogContext
if (configurator instanceof PropertyConfigurator) {
final LogContextConfiguration logContextConfiguration = ((PropertyConfigurator) configurator).getLogContextConfiguration();
clearLogContext(logContextConfiguration);
} else if (configurator instanceof LogContextConfiguration) {
clearLogContext((LogContextConfiguration) configurator);
} else {
// Remove all the handlers and close them as well as reset the loggers
final List<String> loggerNames = Collections.list(EMBEDDED_LOG_CONTEXT.getLoggerNames());
for (String name : loggerNames) {
final Logger logger = EMBEDDED_LOG_CONTEXT.getLoggerIfExists(name);
if (logger != null) {
final Handler[] handlers = logger.clearHandlers();
if (handlers != null) {
for (Handler handler : handlers) {
handler.close();
}
}
logger.setFilter(null);
logger.setUseParentFilters(false);
logger.setUseParentHandlers(true);
logger.setLevel(Level.INFO);
}
}
}
}
代码示例来源:origin: org.wildfly.core/wildfly-cli
final LogContext embeddedLogContext = Holder.LOG_CONTEXT;
final Configurator configurator = embeddedLogContext.getLogger("").detach(Configurator.ATTACHMENT_KEY);
代码示例来源:origin: wildfly/wildfly-core
final LogContext embeddedLogContext = Holder.LOG_CONTEXT;
final Configurator configurator = embeddedLogContext.getLogger("").detach(Configurator.ATTACHMENT_KEY);
内容来源于网络,如有侵权,请联系作者删除!