Oh, right, that's an important consideration...thanks for catching that! I have the two-step configuration working (thanks for the good example) but what's the best way to mirror the application's Spring logging setting? Is there a way to capture what the application settings are for Spring? The way I understand how the two-step configuration works is: 1. Application starts, some logging configured 2. Logging configured for classes that depend on loggers created in step 1. Does step 2 depend on the user of the library (i.e. other developers) creating a 2nd Logback configuration file or is it possible to either ship an appropriate configuration file or to configure logging for the classes in step 2 dynamically? Thanks, Paul On Mon, Oct 24, 2011 at 4:21 PM, ceki <ceki@qos.ch> wrote:
You also mentioned that in addition to the logger named after the class of you custom appender, loggers for the Spring JDBC classes your appender depended on also were initialized with NOPLoggers. If you are interested in the logs from Spring JDBC classes, then your best bet is a two step configuration. -- Ceki
On 24/10/2011 10:17 PM, Paul Gifford wrote:
Thanks Ceki, I'll update my code to use the status manager. Regards, Paul On Mon, Oct 24, 2011 at 3:05 PM, ceki <ceki@qos.ch <mailto:ceki@qos.ch>> wrote:
______________________________**_________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/**listinfo/logback-user<http://mailman.qos.ch/mailman/listinfo/logback-user>