I agree that this might be a useful default in some cases, but how about at least using a separate Logger instance for this, so we can get rid of these warnings without silencing all of RequestCycle's logging?
Cheers, Jonas On Sat, Apr 27, 2013 at 11:12 PM, Igor Vaynberg <[email protected]>wrote: > in many cases this exception will lead to the error page, so its not > just debugging information. this is the case i would rather wicket be > loud by default to help while developing and have interested parties > silence the logger in production systems... > > -igor > > On Sat, Apr 27, 2013 at 11:43 AM, Martin Grigorov <[email protected]> > wrote: > > ivaynberg: ping > > > > > > On Fri, Apr 26, 2013 at 10:59 AM, Jonas <[email protected]> wrote: > > > >> Hi all, > >> > >> after having upgraded to wicket 6.7.0, we get a lot of warnings logged > from > >> RequestCycle.handleException(Exception). Can you please change the > level of > >> 'Handling the following exception' messages to debug, as those warnings > get > >> really annoying. Using level debug, an interested developer still has > the > >> option to see the messages if he's having trouble in that area (by > >> configuring logging accordingly), while you don't nag all other > developers. > >> IMHO log level warn should only be used if it's known something rather > bad > >> is happening, which isn't the case here - this is really just debugging > >> information. > >> > >> Thank you for considering this. > >> > >> Cheers, > >> Jonas > >> > > > > > > > > -- > > Martin Grigorov > > Wicket Training & Consulting > > http://jWeekend.com <http://jweekend.com/> >
