AFAIK, most Cocoon components implement the org.apache.avalon.framework.logger.LogEnable interface. This enables you, principally, to log via log4j or logkit.
Support for logkit is better though: the Cocoon servlet tries to configure logkit via logkit.xconf in [webapp]/WEB-INF. Therefore, if you don't want to change Cocoon source you should log with logkit. If you don't want to tie yourself to logkit you can let your classes implement LogEnabled or use the commons-logging package. See also Wiki Entry from Alan Hodgkinson at http://outerthought.net/wiki/Wiki.jsp?page=JavaLogging Judith > -----Ursprüngliche Nachricht----- > Von: Gernot Koller [SMTP:[EMAIL PROTECTED]] > Gesendet am: Dienstag, 1. Oktober 2002 15:42 > An: [EMAIL PROTECTED] > Betreff: Logging question > > Hi! > > We're developing an application framework within WAS environment, having choosen >Cocoon as our Presentation Framework. Currently our Logging is implemented > via a facade for log4j. I've learned that Cocoon's logging is also somehow based on >log4j. I'm not sure what role the avalon framework plays here. > What I am trying to achieve is unifying our framework's and cocoon's logging. I want >to have on single point, where I can configure the logging, and cocoon > and our framework should be able to potentially log to the same logfile. > Can anybody give me a hint, where the best starting point would be ? Could this be >possible, without modifying cocoon source ? > > thanks, > > Gernot. > > > > --------------------------------------------------------------------- > Please check that your question has not already been answered in the > FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> > > To unsubscribe, e-mail: <[EMAIL PROTECTED]> > For additional commands, e-mail: <[EMAIL PROTECTED]> > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
