I haven't tested it myself, but I'm not sure that ExceptionMappers actually kick-in for exceptions triggered by the underlying Engine.
Regardless of that consideration though, the WebApplicationException thrown in such cases is just a generic one with a 404 status code. Even if I could write an ExceptionMapper to catch it, there'd be no way for me to differentiate it from other 404s. Well, let me rephrase that. I don't see how I'd go about differentiating it, but I'd love to hear your thoughts on the subject :) Regards, Nicola ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2381106
