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=19906>. 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=19906 [ENH] Further logging improvements ------- Additional Comments From [EMAIL PROTECTED] 2003-07-23 20:11 ------- Regarding Marks comments. 1. I disagree, actually. My experience is that it is extremely useful to see exactly what class does the actual logging. Of course, the %c could me moved to the end, or, by suffixing like this: %x{1} it will only print the rightmost part, i.e. only the class name. %{2} will print the class name prefixed by the lowest part og the package name, and so on. (BTW, using %C capital C will always give you the class name, regardless of logger/category, but it is very expensive) 2. I intended to remove the "enabled" flag from the JetspeedPortletStatsService class, but I see I forgot to do so. Right now, you must set the setting as befor, AND configure org.apache.jetspeed.services.portletstats.JetspeedPortletStatsService to INFO or DEBUG, as it logs with INFO. I suggest we remove the enable flag and let all be done by Log4j config. 3. Agree. We should remove all, except what is needed for activating JetspeedLoggingService. 4. Hmmm... Sure you have done all the configuration changes I uploaded? Make sure you have JetspeedLogFactoryService before TurbineLoggingService in the service list in tr.props. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
