geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Dillon <ja...@coredevelopers.net>
Subject Re: logging questions
Date Thu, 18 Sep 2003 01:56:26 GMT
My patch went through James... perhaps I should submit it myself?

--jason


On Wednesday, September 17, 2003, at 09:23  PM, Dain Sundstrom wrote:

> I think Jason sent them a patch way back for the trace level, but I 
> don't think they applied it.  I doubt that they will add my caching 
> code in as it trades off immediate update of log levels for speed.
>
> -dain
>
> On Wednesday, September 17, 2003, at 06:58 AM, Alastair Rodgers wrote:
>
>> Hello Dain,
>>
>> Do you plan to merge any of this stuff (in particular, trace level) 
>> back into the main commons logging source? Just curious.
>>
>> Al.
>>
>>
>>> -----Original Message-----
>>> From: Dain Sundstrom [mailto:dain@coredevelopers.net]
>>> Sent: 16 September 2003 18:52
>>> To: geronimo-dev@incubator.apache.org
>>> Subject: Re: logging questions
>>>
>>>
>>> We use commons logging as the interface for logging in the
>>> code.  Log4J
>>> is the default logging implementation we use, but no code should use
>>> Log4j directly.  We do have a custom implementation of the commons
>>> logging interfaces using Log4j that adds real trace level logging and
>>> caches isXXXEnabled values.
>>>
>>> Anyway, just pretend like Log4j is not there and use commons logging.
>>>
>>> -dain
>>>
>>> On Tuesday, September 16, 2003, at 12:43 PM, n. alex rupp wrote:
>>>
>>>> Do we plan to use a mixture of commons logging and log4j, or is
>>>> someone planning to customize the logging to make it more
>>> fine grained
>>>> (a la jboss logging)?
>>>>
>>>> I noticed both commons logging and log4j are in the
>>> bootlib.  I'm just
>>>> curious where our plans stand regarding them.
>>>>
>>>> Many thanks,
>>>> --
>>>> N. Alex  Rupp (n_alex_rupp@users.sf.net)
>>>
>>>
>
> /*************************
>  * Dain Sundstrom
>  * Partner
>  * Core Developers Network
>  *************************/
>


Mime
View raw message