I'm sorry, but no. They do not come from different loggers. What are you talking about?
We are talking about log4j category loggers. And tapestry is using the classname of the page, and we're using the classname of the page (which is the standard), and hence we can't change the loglevel of what tapestry outputs, without changing the log level of what our own code outputs... Have you seen this on your server? Have you dealt with this yourself? Hugo Palma wrote: > You can differentiate. They come from different loggers. > You can configure log4j(if that's what your using) to ignore(or send to > another appender) DEBUG and TRACE messages from Tapestry. > > Will Norris wrote: >> My concern isn't ERROR and FATAL messages being lost in the noise... >> that can easily be done with some logging configuration as you've >> suggested. My concern is my own DEBUG and TRACE messages being lost >> in the noise, since there is no way to differentiate my own messages >> from those generated by Tapestry. >> >> -will >> >> On Jan 4, 2008, at 10:33 AM, Kalle Korhonen wrote: >> >>> One of the easiest things you can do to combat this problem is to >>> configure >>> logging to output log messages from your application to a separate >>> log file and >>> yet another output for all of those critical ERROR and FATAL messages so >>> they don't get lost in the noise that easily. >>> >>> Kalle >>> >>> >>> On 1/4/08, Fernando Padilla <[EMAIL PROTECTED]> wrote: >>>> >>>> +1 >>>> >>>> We are in the same boat: >>>> >>>> I also dislike the fact that tapestry spits out the generated javacode >>>> using the classname of the page, such that we can't filter it out.. >>>> it's >>>> also hard for us to pay attention to any debug output during the first >>>> few requests. >>>> >>>> >>>> Will Norris wrote: >>>>> I'm running into what must be a common "problem" (bug or feature, you >>>>> decide) though I can't find much info about it in the list archives or >>>>> online. I'm becoming continually frustrated by the fact that the >>>>> TRACE >>>>> and DEBUG log levels are rendered basically useless for pages and >>>>> components because of the amount of logging the framework itself adds. >>>>> I certainly understand the unique difficulty in getting around this >>>>> given how Tapestry works... you can't simply adjust the level for >>>>> different packages like you would in most cases. Is there >>>>> something I'm >>>>> missing that others are doing to alleviate this? Can I turn off >>>>> logging >>>>> from within T5 itself? Is it possible to have T5 use a different >>>>> naming >>>>> convention for the logger name (maybe add "tapestry." to the >>>>> beginning)? How are others handling this? >>>>> >>>>> Thanks, >>>>> Will >>>>> >>>>> --------------------------------------------------------------------- >>>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
