Date: 2004-08-10T12:58:23 Editor: UgoCei <[EMAIL PROTECTED]> Wiki: Cocoon Wiki Page: ButterflyManifesto URL: http://wiki.apache.org/cocoon/ButterflyManifesto
no comment Change Log: ------------------------------------------------------------------------------ @@ -88,6 +88,16 @@ Niclas Hedhman: If everyone follows this rule, then we don't know when there are exceptions to catch, no situations you try to recover from, and we will have runtime unstable systems. Sorry, I don't buy this argument for a second. Programmers need to do there job, not ignore it for the 'time being' as lazy developers will definately do otherwise. Perhaps you can get away with this in a request/response system like Cocoon, but a general recommendation that nothing should throw checked Exception is foolish. +Ugo: I invite everyone to read what others have to say on the subject, then make up your mind: + + * [http://www.mindview.net/Etc/Discussions/CheckedExceptions] + * [http://www.artima.com/intv/jdom3.html] + * [http://www.artima.com/intv/handcuffs.html] + * [http://www.theserverside.com/articles/article.tss?l=RodJohnsonInterview] (read inside the PDF of the sample chapter) + * [http://www.artima.com/intv/solid.html] + +After this, take a careful look at Cocoon's code base and count how many exceptions are swallowed or rethrown as unrelated kind of exceptions (with the ensuing mile-long stacktraces). It's not that checked exceptions are bad in theory. It's that in practice very few developers deal with them sensibly. + == Code == The Subversion repository for Butterfly is [http://svn.apache.org/repos/asf/cocoon/branches/butterfly/ here].
