[ https://issues.redhat.com/browse/WFCORE-482?page=com.atlassian.jira.plugi... ] Andrew Marlow commented on WFCORE-482: -------------------------------------- Thinking some more about wildfly using log4j2, and thinking about java logging in general, I am wondering if this enhancement request is really appropriate. If wildfly was changed then later on it might only need to be changed for log4j version 3, as and when that comes along. IMO it would be better for wildfly to use slf4j to wrap which logger is actually used. Given that wildfly is an application server, it is going to run code in a container where that code could use all sorts of other third party open source components. Those components could contain a mixture of logging approaches. So I think it is up to such components to use slf4j so that they can all play nicely together. If they did and wildfly still picked its own logger then that would be a shame. If on the other hand wildfly used slf4j then if any any contained component didn't that would be the fault of the contained component. Do people agree? If so then perhaps a new ticket should be raised for wildfly to use slf4j. Surely it is the best of both worlds, providing a way for it to still use log4j-v1 for those environments forced to use that logger, and to use log4j2 or logback or whatever, for everyone else. -- This message was sent by Atlassian Jira (v7.13.8#713008)