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 17771] - [PATCH] new logging category never set when using log logicsheet
Date Thu, 29 May 2003 09:30:44 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=17771>.
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=17771

[PATCH] new logging category never set when using log logicsheet





------- Additional Comments From ouzo@vip.net.pl  2003-05-29 09:30 -------
(= getLogger().getChildLogger("...") ).
this one is nice if one would be able to set child category for all logging 
messages. When you use ESQL that is not possible. It is very good for debugging 
to reroute all logging information to another category ( like 
sitemap.xsp.action.myaction1 or sitemap.xsp.data.myquery1 ) and then modify 
logkit.xconf to log all most important information into another file. Maybe 
you're right it's not good to change the category completely, but it would be 
useful to specify child category for the whole script.

Mime
View raw message