commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geir Magnusson Jr." <ge...@adeptra.com>
Subject Re: Logging: more classloader problems.
Date Thu, 06 Jun 2002 19:52:04 GMT
On 6/6/02 3:47 PM, "costinm@covalent.net" <costinm@covalent.net> wrote:

> On Thu, 6 Jun 2002, Geir Magnusson Jr. wrote:
>
>>> Actually the default logger ( used if no 'real' logger is found )
>>> and the JDK1.4 adapter will have to remain in the main jar ( unless
>>> we want to support an alternate impl. for JDK1.4 logging - is it
>>> even possible ? )
>> 
>> Why would it have to remain?
>> 
>> (I'll stop the xposting after this one and keep it on commons...)
> 
> The 'simple' logger ? Because it's very possible ( even likley ) to
> not find any other logger, and it's important to get at least something
> on stderr to know that things don't work. It would be very bad to have
> major errors but see nothing because a logger was not found. Plus for
> simple apps you don't need a real logger.

Sorry - was thinking about the jdk1.4.  Agreed with the default stdout
logger...

> 
> For JDK1.4 ? I don't know, it seems it doesn't work otherwise,
> probably I'm doing something wrong.
> 
> Costin
> 
> 
> 
> 
> 
> 
> --
> To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>
> 

-- 
Geir Magnusson Jr.
Research & Development, Adeptra Inc.
geirm@adeptra.com
+1-203-247-1713



--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message