To provide my own (xml rendering of) error messages, I created a subclass of StatusService as the tutorial suggests (http://www.restlet.org/tutorial#part08).
I install my StatusService in my Application, and that works as expected. I can handle things like missing resources by throwing special exceptions in my Finder classes that get rendered appropriately. But in such cases, when my StatusService is handling things nicely, StatusFilter.doHandle() is still logging a SEVERE message with the exception and stack trace. In such cases I'd rather the log be quiet. I can work around it by overriding handle() in my main router, catching the exception and setting a response status, then _not_ rethrowing. This doesn't feel quite right though. Is there a better way to set this up? Stokes.
