Whoops - that's right, it's getRepresentation(...) rather than getStatus(...). I found that for our project, I had to override getRepresentation in the status service to allow customization of our error responses.
On Wed, Jan 7, 2009 at 5:14 PM, Aron Roberts <[email protected]>wrote: > In the message "Re: StatusService not working", dated 2009-01-07, > Aron Roberts wrote: > > >At 07:23 -0800 2009-01-07, Ganesh wrote: > >>i am trying to add a custom StatusService to my application, that > >>should go to given error page when the resource not found.for the > >>known resources it is going fine..if it is an unknown resource the > >>getStatus is not called!! > > > >In the message "Re: StatusService not working", dated 2009-01-07, > >Stephen Groucutt wrote: > >>Not sure exactly, but could you try overriding getStatus(Status, > >>Request, Response) and see if that works? > > > > From now-hazy memory, it may have also been necessary to enable > >setOverwrite in the parent StatusService instance in order to return > >a error response, rather than Restlet's default response ... > > One more follow-up: the specific classes in StatusService that my > custom status service may have needed to override (at least based on > '@Override' annotations :-), were: > > public Representation getRepresentation( Status status, Request > request, Response response ) {} > > public Status getStatus( Throwable throwable, Request request, > Response response ) {} > > Aron > > ------------------------------------------------------ > > http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1010574 >
