Re: [Prevayler-coders] Exception handling philosophy
Brought to you by:
jsampson,
klauswuestefeld
From: Klaus W. <kla...@gm...> - 2008-04-22 03:28:23
|
Hi Justin, Could you explain these a bit more and give some examples? Thanks, Klaus. On Sun, Apr 20, 2008 at 2:09 PM, Justin T. Sampson <ju...@kr...> wrote: > Howdy, > > I'm getting close to finishing the Git migration. While looking > through the prevayler.org svn commits, I found more of my ideas about > exception handling. Jake will be happy to hear that I had indeed > eventually eliminated SkaringaException. :) As of the svn head, > PrevaylerException, PrevaylerIOException, and PrevaylerError are gone, > with a new PrevalenceError serving some of their purposes. And here's > an interesting comment from that class: > > // Exception-handling notes: > // > // Don't expect checked and unchecked Exceptions to have different semantic > // importance > // > // Never drop or wrap an Error > // > // Never throw a new checked Exception > // > // Throw a PrevalenceError for any abstraction-violating occurrence in > // operation > // > // Throw a RuntimeException for any configuration problems > // > // Never allow the system to continue operating in an inconsistent state > // > // Never hang > > Thoughts? > > Cheers, > Justin > > ------------------------------------------------------------------------- > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference > Don't miss this year's exciting event. There's still time to save $100. > Use priority code J8TL2D2. > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone > _______________________________________________ > Prevayler-coders mailing list > Pre...@li... > https://lists.sourceforge.net/lists/listinfo/prevayler-coders > |