LogManager的替代方案。log4j 2.16.0中log4j 1.2.17中的setRepositorySelector（）

Question

我正在将一个应用程序从log4j 1.2.17转换为2.16.0，在log4j2中，LogManager中似乎不再有setRepositorySelector（）方法。我不能按原样使用Log1.x桥，因为该项目不符合迁移文档中列出的要求。

下面的功能是否有log4j2变通方法？我没有写原始代码，我只是在更新它。

        //The "guard" is a simple object that protects against re-setting of the
        //LoggerFactory by anyone but the one who set it first with a particular
        //"guard".  Basically, this would allow a container to set the LoggerFactory,
        //but disallow applications running in the container from changing it.  If
        //the container holds a handle on the "guard" object, then it alone can
        //change the LoggerFactory.  If no one holds a handle on the "guard" object,
        //then no one can change the LoggerFactory once it is set the first time.       
        Object guard = new Object();
        try {
            LogManager.setRepositorySelector(new ContextJNDISelector(), guard);
        }catch(Exception e){
            System.out.println("Exception, " + CLASS_NAME + ".contextInitialized(): " + e.getMessage());
            //e.printStackTrace();
        }

Answer 1

由于Log4j 2.x API可以有多个实现，因此存储选择器（RepositorySelector）被重命名为上下文选择器（ContextSelector），并移动到Log4jContextFactory。因此，您需要使用：

LogManager.setFactory(new Log4jContextFactory(new JndiContextSelector()));

备注：在任何（直接或间接）调用LogManager之前，必须调用上述代码。getLogger或类似方法。