You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Abhinav Shah (JIRA)" <ji...@apache.org> on 2013/08/17 00:05:47 UTC
[jira] [Created] (LOG4J2-357) log4jConfiguration via log4j.xml on
classpath
Abhinav Shah created LOG4J2-357:
-----------------------------------
Summary: log4jConfiguration via log4j.xml on classpath
Key: LOG4J2-357
URL: https://issues.apache.org/jira/browse/LOG4J2-357
Project: Log4j 2
Issue Type: Bug
Affects Versions: 2.0-beta8
Reporter: Abhinav Shah
I am trying to configure log4j2 for a Web Application.
The documentation says -
{color:red}
"If isLog4jContextSelectorNamed is not true, log4jConfiguration may be a valid URI or a path to a file, or it may start with "classpath:" to denote a file that can be found on the classpath."
{color}
Following is a snippet of my web.xml -
{code:xml}
<context-param>
<param-name>log4jConfiguration</param-name>
<param-value>classpath:log4j/dev.log4j.xml</param-value>
</context-param>
{code}
However, the file dev.log4j.xml is not getting picked up from classpath.
Spring has a similar feature which works fine with log4j 1.x. Please see
{code}
org.springframework.web.util.Log4jWebConfigurer
{code}
--
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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org