>>> {
>>>>> // TODO: handle configuration error
>>>>> }
>>>>> }
>>>>>
>>>>> On Fri, Feb 9, 2018 at 12:37 PM, Ralph Goers <ralph.go...@dslextreme.com>
>>>>> wrote:
>>>
gt;>>>>>
>>>>>> Doh! I thought you had provided me with the magic bullet. :)
>>>>>>
>>>>>> Ok. I'll back to programmically registering info read from my
>>>>>> XmlConfiguration into the active Context.
>>>>>>
gt;>>> wrote:
>>>>>> It occurs to me that there is a problem with my suggest in that you
>>>>>> cannot create a new Configuration using the currently active
>>>>>> configuration as that will cause problems. The current configuration
>>&
t;
>>>>>> wrote:
>>>>>>
>>>>>> If you want to add to their configuration then you should use a
>>>>>> CompositeConfiguration. In that case I would get the current
>>>>>> configuration, create your own Configuration, add them both
s,
>>>>>> it would require that we extract and keep synced the logging
>>>>>> configuration from EVIL.jar, then append our own changes to it. I can
>>>>>> see how this will be helpful when I'm doing development in this
>>>>>> enviro
:
>>>>>> If you want to replace the existing configuration you should be able to
>>>>>> do:
>>>>>>
>>>>>> Configurator.initialize(“MyApp”, “app-log4j2.xml”);
>>>>>>
>>>>>> This will look for a
M, Ralph Goers <ralph.go...@dslextreme.com>
>>>>> wrote:
>>>>>> If you want to replace the existing configuration you should be able to
>>>>>> do:
>>>>>>
>>>>>> Configurator.initialize(“MyApp”, “a
alph Goers <ralph.go...@dslextreme.com>
>>>> wrote:
>>>>> If you want to replace the existing configuration you should be able to
>>>>> do:
>>>>>
>>>>> Configurator.initialize(“MyApp”, “app-log4j2.xml”);
>>>>&
existing configuration you should be able to do:
>>>>
>>>> Configurator.initialize(“MyApp”, “app-log4j2.xml”);
>>>>
>>>> This will look for a file named app-log4j2.xml on the class path.
>>>>
>>>> Ralph
>>>>
>>
me, specificConfig);
> }
> specificConfig.setLevel(level);
> loggerContext.updateLoggers();
>
> see attachment for our full Log4j2Util code.
>
> Regards,
> Volker
>
>
>
> 2018-02-08 21:28 GMT+01:00 Mike Kienenberger <mkien...@gmail.com>:
>>
>
>> Configurator.initialize(“MyApp”, “app-log4j2.xml”);
>>>
>>> This will look for a file named app-log4j2.xml on the class path.
>>>
>>> Ralph
>>>
>>>> On Feb 8, 2018, at 1:28 PM, Mike Kienenberger <mkien...@gmail.com> wrote
t;> Ralph
>>
>>> On Feb 8, 2018, at 1:28 PM, Mike Kienenberger <mkien...@gmail.com> wrote:
>>>
>>> As others have reported in years past, the examples in the docs for
>>>
>>> Programmatically Modifying the Current Configuration after Initializati
itialize(“MyApp”, “app-log4j2.xml”);
>
> This will look for a file named app-log4j2.xml on the class path.
>
> Ralph
>
>> On Feb 8, 2018, at 1:28 PM, Mike Kienenberger <mkien...@gmail.com> wrote:
>>
>> As others have reported in years past, the examples in the
enberger <mkien...@gmail.com
> <mailto:mkien...@gmail.com>>:
> As others have reported in years past, the examples in the docs for
>
> Programmatically Modifying the Current Configuration after Initialization
>
> are out of date. They don't compile. They don't wor
reported in years past, the examples in the docs for
>
> Programmatically Modifying the Current Configuration after Initialization
>
> are out of date. They don't compile. They don't work (affect the
> existing logging) even if you do fix the errors.
>
> Here's
> As others have reported in years past, the examples in the docs for
>
> Programmatically Modifying the Current Configuration after Initialization
>
> are out of date. They don't compile. They don't work (affect the
> existing logging) even if you do fix the errors.
>
> He
As others have reported in years past, the examples in the docs for
Programmatically Modifying the Current Configuration after Initialization
are out of date. They don't compile. They don't work (affect the
existing logging) even if you do fix the errors.
Here's my situation:
I am working
17 matches
Mail list logo
