logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Goers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-432) Fallback when old configuration method is used in servlet 3.0+ container.
Date Thu, 05 Jun 2014 22:04:01 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019341#comment-14019341
] 

Ralph Goers commented on LOG4J2-432:
------------------------------------

Can you please test with the latest in trunk? I believe this has been fixed.

> 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
>
> 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


Mime
View raw message