本文整理汇总了Java中org.apache.logging.log4j.core.appender.AbstractManager.getManager方法的典型用法代码示例。如果您正苦于以下问题:Java AbstractManager.getManager方法的具体用法?Java AbstractManager.getManager怎么用?Java AbstractManager.getManager使用的例子?那么恭喜您, 这里精选的方法代码示例或许可以为您提供帮助。您也可以进一步了解该方法所在类org.apache.logging.log4j.core.appender.AbstractManager
的用法示例。
在下文中一共展示了AbstractManager.getManager方法的3个代码示例,这些例子默认根据受欢迎程度排序。您可以为喜欢或者感觉有用的代码点赞,您的评价将有助于系统推荐出更棒的Java代码示例。
示例1: build
import org.apache.logging.log4j.core.appender.AbstractManager; //导入方法依赖的package包/类
@SuppressWarnings("resource") // actualJmsManager and jndiManager are managed by the JmsAppender
@Override
public JmsAppender build() {
JmsManager actualJmsManager = jmsManager;
JmsManagerConfiguration configuration = null;
if (actualJmsManager == null) {
final Properties jndiProperties = JndiManager.createProperties(factoryName, providerUrl, urlPkgPrefixes,
securityPrincipalName, securityCredentials, null);
configuration = new JmsManagerConfiguration(jndiProperties, factoryBindingName, destinationBindingName,
userName, password, false, reconnectIntervalMillis);
actualJmsManager = AbstractManager.getManager(name, JmsManager.FACTORY, configuration);
}
if (actualJmsManager == null) {
// JmsManagerFactory has already logged an ERROR.
return null;
}
if (layout == null) {
LOGGER.error("No layout provided for JmsAppender");
return null;
}
try {
return new JmsAppender(name, filter, layout, ignoreExceptions, actualJmsManager);
} catch (final JMSException e) {
// Never happens since the ctor no longer actually throws a JMSException.
throw new IllegalStateException(e);
}
}
示例2: getHookableManager
import org.apache.logging.log4j.core.appender.AbstractManager; //导入方法依赖的package包/类
public static <T> HookableOutputStreamManager getHookableManager(final String name, final T data, final ManagerFactory<? extends HookableOutputStreamManager, T> factory) {
return AbstractManager.getManager(name, factory, data);
}
示例3: getManager
import org.apache.logging.log4j.core.appender.AbstractManager; //导入方法依赖的package包/类
/**
* Implementations should define their own getManager method and call this method from that to create or get
* existing managers.
*
* @param name The manager name, which should include any configuration details that one might want to be able to
* reconfigure at runtime, such as database name, username, (hashed) password, etc.
* @param data The concrete instance of {@link AbstractFactoryData} appropriate for the given manager.
* @param factory A factory instance for creating the appropriate manager.
* @param <M> The concrete manager type.
* @param <T> The concrete {@link AbstractFactoryData} type.
* @return a new or existing manager of the specified type and name.
*/
protected static <M extends AbstractDatabaseManager, T extends AbstractFactoryData> M getManager(
final String name, final T data, final ManagerFactory<M, T> factory
) {
return AbstractManager.getManager(name, factory, data);
}