[
https://issues.apache.org/jira/browse/LOG4J2-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13447089#comment-13447089
]
Ralph Goers commented on LOG4J2-18:
-----------------------------------
No. Spring's Log4jWebConfigurer is for Log4j 1.x. You would use Log4j 2's
Log4jContextListener in place of that.
> 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: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
