cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16695] - [PATCH] Log.xsl logicsheets creates invalid logging category
Date Wed, 05 Mar 2003 18:07:59 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16695>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16695

[PATCH] Log.xsl logicsheets creates invalid logging category





------- Additional Comments From ouzo@vip.net.pl  2003-03-05 18:07 -------
This is odd, yes, but if you prepend logging category with cocoon - all 
messages end up in tomcat's log. When category is "sitemap" instead 
of "cocoon.sitemap" everything is where it should be. Maybe this is caused by 
some core component change but currently the logging category shouldn't 
have "cocoon." prefix. 

this is a snippet from my code and it works properly:
try {
  org.apache.log.Logger logger =
    org.apache.log.Hierarchy.getDefaultHierarchy().getLoggerFor
("sitemap.myapp.myaction");
  logger.setPriority(org.apache.log.Priority.getPriorityForName("DEBUG"));
  this.enableLogging(new org.apache.avalon.framework.logger.LogKitLogger
(logger));
} catch (Exception e) {
    getLogger().error( "Error setting myapp logger" );
}

Mime
View raw message