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] > >
