[NAS-1729] Update exception handling strategy Created: 09/Jun/09 Updated: 16/Jun/11 |
|
Status: | Open |
Project: | NetarchiveSuite |
Component/s: | Common |
Affects Version/s: | 3.8 |
Fix Version/s: | None |
Type: | New Feature | Priority: | Minor |
Reporter: | Nicolas Giraud (Inactive) | Assignee: | Unassigned |
Resolution: | Unresolved | ||
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Organization: |
General
|
Description |
Currently the very few existing application exceptions inherit from dk.netarkivet.common.exceptions.NetarkivetException which itself extend RuntimeException.
|
Comments |
Comment by Mikis Seth Sørensen (Inactive) [ 16/Jun/11 ] |
Ohhh, and of course it should be possible to define new exception types in all modules. |
Comment by Mikis Seth Sørensen (Inactive) [ 16/Jun/11 ] |
We recently discussed this and agreed that the Exception handling strategy used in the Bit Repository project. Both Mikis and Jonas (and Kåre, forme NAS guy) participates in this project, where the exception strategy is based on the NAS strategy with modifications for the shortcomes found here. Comparing the concerns listen in this issue and the Bit Repository strategy:
Note that the idea of clearly defined fault barriers are crucial to the idea of using unchecked exceptions. A natural place to implement fault barriers are when creating new threads (not the only place). NAS could certainly use a consolidation in this area. |
Comment by Mikis Seth Sørensen (Inactive) [ 17/Nov/09 ] |
svc - svc@kb.dk - 06/10/2009 10:17:14 svc - svc@kb.dk - 11/30/2009 16:13:31 |