Bertrand Delacretaz wrote:
On Dec 31, 2007 12:37 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
...I think we should drop the
HttpStatusCodeException as it seems a little bit wired to transfer a
status code by throwing an exception....
As the one who introduced the HttpStatusCodeException, I'd rather keep it ;-)
Is "looking for a Resource and not finding it" not an exception?
I think
throw new HttpStatusCodeException(404,"Did not find resource " +
resourceName);
is a very clear way of handling such a case, and it's also easy to
verify in automated tests.
Yes, I think this is true for the 404 case, but what about other status
codes? So perhaps a ResourceNotFoundException makes more sense?
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
