Hi Philip, your intuition is good, this message comes from the getStatus() method of the StatusFilter class. The way you describe seems good too. I'm not sure the whole solution has been designed just in order to obtain easily the requested information, that's why it seems quite complex. Jerome, what do you think about?
best regard, Thierry Boileau > Greetings, > > My Restlet-based server is occasionally printing out the following to the > console: > > Unhandled exception or error intercepted > > Without any additional information. I have a couple of questions: > > (1) This appears to be generated by the getStatus() method of the StatusFilter > class. (I can't tell for sure, because I don't have a stack trace.) > StatusFilter extends Filter, and the JavaDoc indicates I could override this > method in a subclass to customize the behavior. > > I create an Application instance, which has a setStatusService(StatusService) > method, and StatusService has a getStatus() method. So, if I wanted to get > additional details about the nature of my unhandled exceptions, should I > create a subclass of StatusService with its own getStatus() method and bind > it to myApplication instance using setStatusService()? This seems like a > lot of complexity for a minor requirement, so my question is: > > What is the best way to obtain additional information about such "unhandled > exceptions"? > > (2) Wouldn't it be better if the Restlet getStatus() method were modified to > print the stack trace by default so that the default behavior would provide > more useful information? > > Thanks very much for any insights you can provide. I might be very confused, > so don't hesitate to straighten me out. > > Philip > > >
