[Jboss-dev-forums] [Design of Mail Services] - Re: Exception Handling

[<aco...@jb...>]

overall I think tis good but i think all exceptions should be runtime exceptions.  If you choose to catch it locally, then fine.

the state/conversational nature of the protocol doesn't always allow them to be caught at the entry point and I'm unsure that this will make the code cleaner.  

I think that we have 4 types:

1. Stream killers (so don't bother telling the user)
2. It didn't taste good/stream ok (so tell the user)
3. detached exceptions (couldn't deliever so maybe tell the user by sending him a "couldn't deliver" email preferrably with more detail than we have today!!!)
4. Panics (SQL Exception is a BAD BAD error, tell someone, bad stuff is happening, we've lost the DB, we have deadlocks, fix us!!!) -- we may want to do service unavailable rather than accept messages that won't be delivered.

-Andy

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884437#3884437

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884437