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 Sun, 11 May 2003 09:30:14 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 bruno@outerthought.org  2003-05-11 09:30 -------
You are right that the getLogger() == null test makes the rest of the code quite
useless. Since XSP's always extend from AbstractLogEnabled, this will never be
null anyway.

But your patch (or the code that was already there) is conceptually wrong (IMO),
it basically introduces a parallel logging system. It would be way better to
create child loggers on the existing logger (= getLogger().getChildLogger("...") ).

Alternatively, you can configure multiple serverpagesgenerators in the sitemap,
and assign them different loggers.

Mime
View raw message