[jira] [Closed] (LOG4J2-432) Fallback when old configuration method is used in servlet 3.0+ container.

["Remko Popma (JIRA)" <ji...@apache.org>]

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

Remko Popma closed LOG4J2-432.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0-rc1

Closing this issue as the reporter confirmed the problem was fixed in RC1.

> Fallback when old configuration method is used in servlet 3.0+ container.
> -------------------------------------------------------------------------
>
>                 Key: LOG4J2-432
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-432
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0-beta9
>         Environment: Jetty 9.x
>            Reporter: Xavier Cho
>             Fix For: 2.0-rc1
>
>
> Currently, when the Log4jServletFilter/Log4jServletContextListener are explictly configured in a web.xml, the application will fail to start on some Servlet 3.0+ container like Jetty 9.x.
> For some type of projects, providing two different versions of war packages just to avoid this problem is not a viable option.
> Maybe we better just warn the user instead of an throwing UnavailableException when the old method is used in Servlet 3.0 environment?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org