* Ivo van Dongen: > I have a problem with error logging strategies. In our > application, we use a log4j SMTP appender, that sends out > alarming emails in case of error logs. However, we cannot > properly control our wicket application as far as logging is > concerned. The problem is that this causes us to receive emails, > for instance, when a user enters an incorrect URL - which is > hardly alarming, I'd say.
You may be interested in this bug report: PackageRequestTargetUrlCodingStrategy should interrupts the cycle and sends a 404 when a page/class cannot be found http://issues.apache.org/jira/browse/WICKET-293 If there is massive user feedback about this one, it may gain more attention ;-) > I'd say one should allow more control: why not call a > protected method that has a default implementation of > log.error(e.getMessage, e) ? This way, one can easily adjust the > logging level by overriding this method in a subclass. Check out the latest code, a new protected method has been added just for that. -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/
