http://www.factorypattern.com/wrapping-checked-exceptions-java/ Just another Object Oriented Weblog Fri, 12 Feb 2010 18:48:20 -0700 http://wordpress.org/?v=2.9.1 hourly 1 http://www.factorypattern.com/wrapping-checked-exceptions-java/comment-page-1/#comment-81 owen Fri, 26 Sep 2008 14:25:10 +0000 http://www.factorypattern.com/wrapping-evilchecked-exceptions-in-java/#comment-81 I've always found exceptions to be heavily mis-used often like goto statements replacing proper logic blocks and good coding practices. I’ve always found exceptions to be heavily mis-used often like goto statements replacing proper logic blocks and good coding practices.

]]> http://www.factorypattern.com/wrapping-checked-exceptions-java/comment-page-1/#comment-40 Torgny Andersson Wed, 27 Aug 2008 19:26:10 +0000 http://www.factorypattern.com/wrapping-evilchecked-exceptions-in-java/#comment-40 To me, the best solution is to wrap the exception thrown AND provide an additional description of what went wrong. Example: StartupException["Failed to configure application.", ConfigurationException["Failed to open configuration file: something.conf", IOException["file not found"]]] This has two benefits: 1) The exception description is very general at the top and is more and more detailed for the wrapped exception, which makes it easier to put the originating exception into a context. 2) The entire stack-trace is kept, which makes it easier to track down the problem. To me, the best solution is to wrap the exception thrown AND provide an additional description of what went wrong. Example:
StartupException["Failed to configure application.", ConfigurationException["Failed to open configuration file: something.conf", IOException["file not found"]]]
This has two benefits:
1) The exception description is very general at the top and is more and more detailed for the wrapped exception, which makes it easier to put the originating exception into a context.
2) The entire stack-trace is kept, which makes it easier to track down the problem.

]]> http://www.factorypattern.com/wrapping-checked-exceptions-java/comment-page-1/#comment-39 Mike Wed, 27 Aug 2008 13:15:18 +0000 http://www.factorypattern.com/wrapping-evilchecked-exceptions-in-java/#comment-39 When you wrap an exception, you should try to provide at least as much information as the original exception, if not more. Don't forget to include all of the original <a href="http://72miles.com/blog/posts/exceptional-meta-data/" rel="nofollow">exception's meta data</a>, and consider adding your own. When you wrap an exception, you should try to provide at least as much information as the original exception, if not more. Don’t forget to include all of the original exception’s meta data, and consider adding your own.

]]>