From: mikezzz <nu...@jb...> - 2005-07-12 17:10:46
|
I think 2 & 3 are the same (MDBs are entry points in their own special way :-). Sending an 'couldn't deliver' email is exception handling rather than an a type of exception. I see these as 2 orthoginal concepts. I am happy to use RuntimeExceptions for all exceptions, but would like to have seperate base exceptions to distingush different types. Looking closer at the protocols I see what you mean about the conversation state stuff. However if we choose to handle the error locally then we should make sure something useful is returned to the caller. Either return a valid object or throw an exception. We shouldn't swallow the exception, log it and return null. There are few cases where this happens and the protocol gets into an unknown state, throws a null pointer exception and falls over in a heap. Also people tend to forget to check for nulls (I know I do). Cleanliness will hopefully be a result of a consistent approach. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884561#3884561 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884561 |