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 "Remko Popma (JIRA)" <ji...@apache.org> on 2015/10/13 06:56:05 UTC
[jira] [Updated] (LOG4J2-873) WebLookup shouldn't require
display-name element in web.xml
[ https://issues.apache.org/jira/browse/LOG4J2-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Remko Popma updated LOG4J2-873:
-------------------------------
Fix Version/s: (was: 2.4.1)
2.5
> WebLookup shouldn't require display-name element in web.xml
> -----------------------------------------------------------
>
> Key: LOG4J2-873
> URL: https://issues.apache.org/jira/browse/LOG4J2-873
> Project: Log4j 2
> Issue Type: Bug
> Components: Web/Servlet
> Affects Versions: 2.0.2
> Reporter: Martin Dickins
> Assignee: Ralph Goers
> Priority: Minor
> Fix For: 2.5
>
>
> The initializeNonJndi method in Log4jWebInitializerImpl uses servletContext.getServletContextName() to get a context name (if the name hasn't been defined using log4jContextName). getServletContextName() returns the name as specified in the <display-name> element in web.xml, but that is optional.
> If neither <display-name> nor log4jContextName is defined, this results in the servletContext not being set, so the WebLookup doesn't work.
> It should use some sort of default. Probably the name of the war file or context file, if there's a generic way of getting that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org