istensen [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 04, 2001 5:29 PM
To: LOG4J Developers Mailing List
Subject: Re: Adding Hashtable to LoggingEvent [WAS: Recent commit by
Paul]
IMHO, we should not add a Hashtable to LoggingEvent to address
brittleness of serialized LoggingEvents and probably n
ülcü <[EMAIL PROTECTED]> on 06/04/2001 02:16:39 PM
>
>Please respond to "LOG4J Developers Mailing List"
> <[EMAIL PROTECTED]>
>
>To: "LOG4J Developers Mailing List" <[EMAIL PROTECTED]>
>cc:
>Subject: Re: Recent commit by Paul
>
ervices
818 539 3321
Ceki Gülcü <[EMAIL PROTECTED]> on 06/04/2001 02:16:39 PM
Please respond to "LOG4J Developers Mailing List"
<[EMAIL PROTECTED]>
To: "LOG4J Developers Mailing List" <[EMAIL PROTECTED]>
cc:
Subject: Re: Recent commit by Paul
IMHO, we should not add a Hashtable to LoggingEvent to address
brittleness of serialized LoggingEvents and probably not for any other
reason either.
If a particular Appender (a derivative of SocketAppender perhaps) wants
to serialize LoggingEvents as a set of string name-value pairs or XML
encode
At 10:43 04.06.2001 -0700, you wrote:
>Ceki,
>
>The PropertyConfigurator only sets the default category factory when
>someone has specified that a different category factory be used (via the
>categoryFactory property). Without this behaviour, we are saying go ahead
>and specify any factory you
AIL PROTECTED]> on 06/04/2001 09:56:50 AM
Please respond to "LOG4J Developers Mailing List"
<[EMAIL PROTECTED]>
To: "LOG4J Developers Mailing List" <[EMAIL PROTECTED]>
cc:
Subject: Re: Recent commit by Paul
Hello Paul,
Having the PropertyConfigura
818 539 3321
>
>
>Ceki Gülcü <[EMAIL PROTECTED]> on 06/04/2001 12:55:24 AM
>
>Please respond to "LOG4J Developers Mailing List"
> <[EMAIL PROTECTED]>
>
>To: "LOG4J Developers Mailing List" <[EMAIL PROTECTED]>
>cc:
&g
respond to "LOG4J Developers Mailing List"
<[EMAIL PROTECTED]>
To: "LOG4J Developers Mailing List" <[EMAIL PROTECTED]>
cc:
Subject: Recent commit by Paul
Hello Paul,
The recent addition of
Category.getDefaultHierarchy().setCategoryFactory(categoryFactory);
in co
Hello Paul,
The recent addition of
Category.getDefaultHierarchy().setCategoryFactory(categoryFactory);
in configureCategoryFactory method in PropertyConfigurator.java is troublesome.
Setting the category factory once and fall al may be suitable in certain cases but
precludes different ex
