[
https://issues.apache.org/jira/browse/LOG4J2-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13867211#comment-13867211
]
Giovanni Mondo commented on LOG4J2-484:
---------------------------------------
Trying the example I posted on an XP (after Fedora and Windows 7) logged only
on default_MavenWeb.log as you said :-( , but setting
<context-param>
<param-name>isLog4jContextSelectorNamed</param-name>
<param-value>false</param-value>
</context-param>
I finally have what I would like: listeners and servlet logging on the same
MavenWeb.log .
Is it right to set isLog4jContextSelectorNamed to false ? Is this a stable
result or could change in next releases, in a different environment ... ?
> 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: MavenWeb2.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
