[logback-user] I'm getting the "substitute logger" error message yet my appender still works

[Paul Gifford]

Wow...that was easy...thanks!

Paul

On Mon, Oct 24, 2011 at 4:50 PM, ceki <ceki at qos.ch> wrote:

> Simply move the configuration of your custom appender to another
> secondary configuration file. Load this file in a second configuration
> step. That's it. You don't have to worry about loggers references by
> Spring classes.
> --
> Ceki
> http://twitter.com/#!/ceki
>
>
> On 24/10/2011 10:45 PM, Paul Gifford wrote:
>
>> 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
>>
>>
>
>  ______________________________**_________________
> Logback-user mailing list
> Logback-user at qos.ch
> http://mailman.qos.ch/mailman/**listinfo/logback-user<http://mailman.qos.ch/mailman/listinfo/logback-user>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.qos.ch/pipermail/logback-user/attachments/20111024/19c23688/attachment.html>