Configuration is not part of the public API - it is very implementation
specific. So Configurator is part of log4j-core. However, we expect it to be
used by applications so it is one of the classes in core where we try to
maintain binary compatibility.
Ralph
> On Jun 17, 2016, at 6:15 AM, Joch
Configurator is in log4j-core.
On 17 June 2016 at 08:15, Jochen Wiedmann wrote:
> On Fri, Jun 17, 2016 at 3:07 PM, Ralph Goers
> wrote:
> > You would use Configurator.initialize(“MyContextName”,
> this.getClass().getClassLoader(), uri);
> >
> > The classLoader value can be null.
>
> Thanks, Ral
On Fri, Jun 17, 2016 at 3:07 PM, Ralph Goers wrote:
> You would use Configurator.initialize(“MyContextName”,
> this.getClass().getClassLoader(), uri);
>
> The classLoader value can be null.
Thanks, Ralph. One question, though:
The class Configurator is not present on
http://logging.apache.or
I would probably use tenantName for the context name.
Ralph
> On Jun 17, 2016, at 6:07 AM, Ralph Goers wrote:
>
> You would use Configurator.initialize(“MyContextName”,
> this.getClass().getClassLoader(), uri);
>
> The classLoader value can be null.
>
> Ralph
>
>> On Jun 17, 2016, at 1:41 A
You would use Configurator.initialize(“MyContextName”,
this.getClass().getClassLoader(), uri);
The classLoader value can be null.
Ralph
> On Jun 17, 2016, at 1:41 AM, Jochen Wiedmann
> wrote:
>
> Hi,
>
> I have an application (more precisely: a war file), which is deployed
> identically on
