> 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.
Yep. If you create a custom request cycle now, you can override
logRuntimeException(RuntimeException). Don't call super in there when
you don't want it to be logged without interference. Also
onRuntimeException(Page, RuntimeException) is always called if you
want more control over what is displayed to users.
Eelco
