[
https://issues.apache.org/jira/browse/LOG4J2-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roger Bisson resolved LOG4J2-748.
---------------------------------
Resolution: Fixed
Fix Version/s: 2.0.1
> Erroneous references to log4j classes appearing in online documentation
> -----------------------------------------------------------------------
>
> Key: LOG4J2-748
> URL: https://issues.apache.org/jira/browse/LOG4J2-748
> Project: Log4j 2
> Issue Type: Documentation
> Components: Documentation
> Affects Versions: 2.0
> Reporter: Roger Bisson
> Fix For: 2.0.1
>
>
> On the following page
> [http://logging.apache.org/log4j/2.x/manual/webapp.html], at the section
> entitled "Servelet 2.5 Web Applications", there are references to the
> following listener and filter classes -
> {{org.apache.logging.log4j.core.web.Log4jServletContextListener}}
> {{org.apache.logging.log4j.core.web.Log4jServletFilter}}
> When the web.xml settings provided in this particular section are used in
> conjunction with Apache Tomcat, Tomcat logs a relatively obscure error to the
> effect the relevant listener and filter could not be started.
> The problem has been traced to an incorrect classpath. The correct classes
> and associated classpaths ought to be -
> {{org.apache.logging.log4j.web.Log4jServletContextListener}}
> {{org.apache.logging.log4j.web.Log4jServletFilter}}
> "*core*" has been omitted from each. For the benefit of future log4j2
> developers, it may be helpful to update the documentation to refer to the
> correct classes.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org
