[ https://issues.jboss.org/browse/WFCORE-482?page=com.atlassian.jira.plugin... ] Steve Cohen commented on WFCORE-482: ------------------------------------ Coming over here after your post on[ Stack Overflow|http://stackoverflow.com/questions/40476703/log4j2-logging-of-co...]. The answers to your questions are very much in flux. As I said on Stack Overflow: {quote}I am doing the following: porting several legacy applications from WebLogic to JBoss EAP 7. Some of the components being ported are EJBs. Others are servlet apps that invoke these EJBs. These EJBs are deployed in ejb-jars. I know that I could wrap this whole thing into a big EAR file but we don't want to do that. The servlets and the EJB jars need to be separately deployable components. Then there is the logging setup. We are using log4j2 and we want to keep independent of the JBoss logging setup. I have created a JBoss module that contains all the log4j2 jars with the proper dependencies, and logging works. The servlet runs and logs, invokes the EJBs and they work. The only problem is how to configure the EJB's logging. In a Web App like the servlet, it's easy, just specify the log4j logging configuration file in web.xml. What's the analog for an ejb jar? I couldn't think of a way. {quote} I had no idea I was so far out on the bleeding edge. If you can supply an example of successfully using the LoggerContextFactory I would love to see it. That section of log4j documentation is very weak. -- This message was sent by Atlassian JIRA (v7.2.3#72005)