[
https://issues.apache.org/jira/browse/LOG4J2-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447070#comment-13447070
]
Ralph Goers commented on LOG4J2-18:
-----------------------------------
I have tested with JBoss 5 with a web app using SLF4J mapped to Log4j 2 using
the Log4jContextListener. This works, however SLF4J is complaining that there
are multiple SLF4J bindings. So far I have not been successful in eliminating
this. Luckily it is choosing the binding within the web app so the application
is behaving properly.
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
