While I don't agree with the proposal to move from logkit to log4j, I'm not sure why CocoonServlet has DefaultLogKitManager hardcoded in it - especially since that class is deprecated. It seems to me that I should be able to configure Cocoon to use any implementation of LoggerManager, including Log4JLoggerManager or my own custom implmentation. The default could be DefaultLoggerManager (which requires that the "real" LoggerManager be configured), or LogKitLoggerManager.
Ralph > -----Original Message----- > From: Jorg Heymans [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 28, 2003 4:18 AM > To: '[EMAIL PROTECTED]' > Subject: RE: Porting Cocoon Logging to Log4j - Proposal and Discussion > > > Reading up on the wiki > http://wiki.cocoondev.org/Wiki.jsp?page=ConfiguringTheLogs > > it seems that all of the stuff you want can be done already > using the avalon > logging factories. > > It looks maybe a bit more complicated to setup but I'm sure > that once you > can configure async JMS logging in log4j you shouldn't have > much problem > doing the same for avalon. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
