>> But why throwing a ProcessingException ? Simply throwing Exception would >> avoid exception cascading (I hate these never ending stacktraces) and >> better cope with the variety of implementations. >> > Valid question...now the question is: where do you want to handle the > exception? > If you throw just Exception than the calling code has to test, if the > thrown Exception is a wrapping or non-wrapping exception if it catches > the exception. This results in rather ugly code with several catch > statements. > If you throw ProcessingException than the component has to do this > conversion - personally I like this approach more. > > But if you want, we can "change" this to just Exception.
Please no, Exception is meaningless. I'd prefer that people are always be as specific as possible about what went wrong, if someone doesn't want to handle a specific problem, that's their decision, but don't stop the rest of us from knowing why something blew up... --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
