> On Sep 27, 2020, at 11:07 AM, Jochen Wiedmann
> wrote:
>
> On Sun, Sep 27, 2020 at 6:38 PM Ralph Goers
> wrote:
>>
>> It would not create a new LoggerContext. But a ConfigurationSource
>> represents an entire configuration. So calling initialize with it would
>> cause a new Configuratio
On Sun, Sep 27, 2020 at 6:38 PM Ralph Goers wrote:
>
> It would not create a new LoggerContext. But a ConfigurationSource represents
> an entire configuration. So calling initialize with it would cause a new
> Configuration to be created. So yes, all your existing LoggerConfigs would be
> repla
It would not create a new LoggerContext. But a ConfigurationSource represents
an entire configuration. So calling initialize with it would cause a new
Configuration to be created. So yes, all your existing LoggerConfigs would be
replaced by the new configuration. Loggers would be unaffected as
LoggerContext is a bridge object for controlling the underlying
configuration. It doesn’t change, but its state and Configuration instance
does.
On Sun, Sep 27, 2020 at 10:46 Jochen Wiedmann
wrote:
> Thanks, Ralph,
>
>
>
> but that would create a new LoggerContext, wouldn't it? (Thus,
>
> invali
Thanks, Ralph,
but that would create a new LoggerContext, wouldn't it? (Thus,
invalidating my existing loggers.)
Jochen
On Sun, Sep 27, 2020 at 5:08 PM Ralph Goers wrote:
>
> Try calling
>
> Configurator.initialize(null, configurationSource);
>
> Ralph
>
> > On Sep 27, 2020, at 7:40 AM, Jochen
Try calling
Configurator.initialize(null, configurationSource);
Ralph
> On Sep 27, 2020, at 7:40 AM, Jochen Wiedmann
> wrote:
>
> Hi,
>
> in LoggerContext, I have
>
>void updateLoggers(Configuration);
>
> I understand, that this method provides the means to change the logging
> config
Hi,
in LoggerContext, I have
void updateLoggers(Configuration);
I understand, that this method provides the means to change the logging
configuration at runtime. Very well!
Problem is: I do not have a Configuration, but a ConfigurationSource.
So, what to do?
Thanks,
Jochen
--
Look, th