[jira] [Commented] (LOG4J2-18) Better compatibility with JBoss

["Matt Sicker (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917647#comment-13917647 ] 

Matt Sicker commented on LOG4J2-18:
-----------------------------------

So, uh, is this still a valid issue now that JBoss/WildFly uses JBoss-Logging which reminds me of commons-logging as it is?

> Better compatibility with JBoss
> -------------------------------
>
>                 Key: LOG4J2-18
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-18
>             Project: Log4j 2
>          Issue Type: Improvement
>         Environment: JBoss and perhaps other "containers"
>            Reporter: Ralph Goers
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org