[logback-user] Jetty conflict

Thorbjoern Ravn Andersen ravn at runjva.com
Thu Feb 4 19:31:31 CET 2010

Ceki Gülcü skrev:
> Interestingly enough, jetty considers org.apache.log4j and 
> org.apache.commons.logging as *system* classes which the web-app 
> cannot override. I am sure there are good reasons for this strategy 
> but it does not affect slf4j users, unless of course they are using 
> log4j or if they are using jcl-over-slf4j.
If applications are used using Jetty contexts everything is overridable.

The Jetty configuration file format is just a thin XML-layer on top of a 
quite sophisticated object creation  hierarchy.  Hence my suggestion to 
use it in logback.

  Thorbjørn Ravn Andersen  "...plus... Tubular Bells!"

More information about the Logback-user mailing list