|
Well, yes and no. Realistically what can the application do at this point if persistence fails? Whether it's a DB/persistence exception or something general like a null pointer exception the app will pretty much do the same thing. I think it's probably best to throw a new exception (wrapping the old one) that the app can handle in some what that makes sense to the user. If the app really can do something different depending on the error then it can still check the wrapped exception. If not it can print a message to the user explaining what happened. |
java.net RSS Feeds
