[LOG4J2-18] Better compatibility with JBoss

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Invalid

Environment

JBoss and perhaps other "containers"

• Assignee: Ralph Goers
• Reporter: Ralph Goers
• Created: 22/Jun/08 22:42
• Updated: 18/Jun/19 04:37
• Resolved: 18/Jun/19 04:37

Description

JBoss currently uses log4j for its own logging purposes. This causes numerous problems for applications that also want to use log4j for logging. JBoss has some documented methods for addressing the problems but none of them are particularly attractive. The goals for this issue should be:
1. Allow each "application" to have its own configuration separate from JBoss' jboss-log4j.xml
2. Allow applications to provide their own log4j components (Appenders, layouts, filters, etc) without having to put them in JBoss' classpath or the server/lib directory.

Issue Links

• relates to: LOG4J2-546 Commons logging integration does not work in WildFly 8.0