cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marco Rolappe" <m_rola...@web.de>
Subject AW: [RT] Logging in Cocoon
Date Thu, 27 May 2004 14:55:31 GMT


> -----Ursprungliche Nachricht-----
> Von: dev-return-61511-m_rolappe=web.de@cocoon.apache.org
> [mailto:dev-return-61511-m_rolappe=web.de@cocoon.apache.org]Im Auftrag
> von Carsten Ziegeler
> Gesendet: Donnerstag, 27. Mai 2004 16:40
> An: dev@cocoon.apache.org
> Betreff: RE: [RT] Logging in Cocoon
> 
> 
> Marco Rolappe wrote: 
> > 
> > the only problem I have with directly using log4j is being 
> > tied to it. if the code starts to use log4j specific features 
> > you'll be no more (easily) able to move to another logger 
> > implementation. and the issues with commons-logging 
> > (classpath, etc.) will probably also be true for log4j.
> > 
> Ah, ok, I see. Now, I wasn't very clear what I meant. Of course,
> I would like to have the used logging system still configurable
> like it is today. Today we ship Cocoon with LogKit preconfigured.
> What I meant is to change this to Log4j.
> 
> As this is only the logging subsystem used by Avalon logging,
> no code of Cocoon has to be changed and we will not use log4j
> directly from our code. So we should be able to switch at
> any time.

okay, that clears everything up. nun sind alle klarheiten beseitigt ;-)


Mime
View raw message