logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Remko Popma (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (LOG4J2-873) Omitting display-name element in web.xml causes incorrect log4j initialization
Date Fri, 23 Oct 2015 18:16:27 GMT

     [ https://issues.apache.org/jira/browse/LOG4J2-873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Remko Popma updated LOG4J2-873:
-------------------------------
    Summary: Omitting display-name element in web.xml causes incorrect log4j initialization
 (was: WebLookup shouldn't require display-name element in web.xml)

> Omitting display-name element in web.xml causes incorrect log4j initialization
> ------------------------------------------------------------------------------
>
>                 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
>             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


Mime
View raw message