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

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-beta9
• Fix Version/s: 2.0-rc1
• Component/s: Core

Environment

Jetty 9.x

• Assignee: Unassigned
• Reporter: Xavier Cho
• Created: 17/Oct/13 07:42
• Updated: 26/Jul/14 14:12
• Resolved: 26/Jul/14 14:12

Description

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?