Uploaded image for project: 'Log4j 2'
  1. Log4j 2
  2. LOG4J2-432

Fallback when old configuration method is used in servlet 3.0+ container.

    XMLWordPrintableJSON

    Details

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

      Jetty 9.x

      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?

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              mysticfall Xavier Cho
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: