[
https://issues.apache.org/jira/browse/LOG4J2-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867367#comment-13867367
]
Remko Popma commented on LOG4J2-484:
------------------------------------
The behaviour you describe is documented in the manual page on [Web
Applications and
JSPs|http://logging.apache.org/log4j/2.0/manual/webapp.html#ContextParams]. So
you can assume this is stable.
Personally, my recommendation would be to keep it simple and just have one
log4j2.xml config file per web application (and test to ensure that the
configuration paths are correct). But that is just me...
> log4j2 and ServletContextListeners
> ----------------------------------
>
> Key: LOG4J2-484
> URL: https://issues.apache.org/jira/browse/LOG4J2-484
> Project: Log4j 2
> Issue Type: Question
> Components: Configurators
> Affects Versions: 2.0-beta9
> Environment: java 1.7.0_11-b21, tomcat-7.0.14
> Reporter: Giovanni Mondo
> Priority: Trivial
> Labels: newbie
> Fix For: 2.0-rc1
>
> Attachments: MavenWeb3.zip
>
>
> Logging configuration is done by two config file:
> WEB-INF/classes/log4j2.xml logging in /tmp/default_MavenWeb.log
> and
>
> /tmp/final_log4j2.xml as log4jConfiguration of a Log4jServletContextListener
> logging in /tmp/MavenWeb.log
>
> Is it possible to log HelloWorldServletContextListener in /tmp/MavenWeb.log
> as HelloWorldServlet does ?
> A minimal maven project with full details can be found in attachment.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
