Hi all,
After all the feedback and some silent time, I updated the Wiki [1] and
the prototype [2] as follows:
* Remove HttpStatusCodeException
* Add ResourceNotFoundException
I noone objects, I will start implementing these changes to the API
sometime next week and also start adapting the uses throughout the
repository.
Regards
Felix
[1] http://cwiki.apache.org/confluence/x/DR4B
[2]
http://svn.apache.org/repos/asf/incubator/sling/whiteboard/fmeschbe/effective_exceptions
Am Samstag, den 29.12.2007, 20:58 +0100 schrieb Felix Meschberger:
> Hi all,
>
> Prompted by a blog by Alexander Klimetschek [1] and a very interesting
> paper on exceptions [2] I set back to think about the exceptions in the
> Sling API and wrote a wiki page on this subject [3].
>
> To summarize, we should make the SlingException a RuntimeException and
> all exceptions defined in the Sling API extend SlingException. Together
> with appropriate catching inside Sling itself (letting RuntimeExceptions
> pass through generally) this should help us streamline exception
> handling.
>
> A prototype API definition may be found in the whiteboard at [4].
>
> What do you think ?
>
> Regards
> Felix
>
> [1]
> http://weblogs.goshaky.com/weblogs/alexkli/entry/exception_best_practices
> [2] http://dev2dev.bea.com/pub/a/2006/11/effective-exceptions.html
> [3] http://cwiki.apache.org/SLING/effective-exceptions.html
> [4]
> http://svn.apache.org/repos/asf/incubator/sling/whiteboard/fmeschbe/effective_exceptions
