On Jan 7, 2008 12:18 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > ...Hmm, yes that's true. But do we really need this? I agree that an > exception for > the resource not found case is needed. But why do we need a special > exception for internal server error? Doesn't throwing any other > exception state the same?...
After rereading this thread and looking at how HttpStatusCodeException is used in microsling code, I agree with you: we should have a ResourceNotFoundException, and use the HttpServletResponse interface to set other status codes. Do others agree with that? > ...I'm not sure if indicating a redirect back to the error handler makes > sense? I would rather expect that the code sends the redirct status > instead of throwing an exception... Agreed as well. -Bertrand
