Changes between Version 3 and Version 4 of GeoNetworkException


Ignore:
Timestamp:
Dec 1, 2008, 10:22:32 AM (16 years ago)
Author:
heikki
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GeoNetworkException

    v3 v4  
    11One or more general exception are needed to organise exception handling in the application.
    22
    3 '''Option 1:''' GeoNetworkException extends java.lang.RuntimeException
     3'''Option 1:''' GeoNetworkException extends java.lang.!RuntimeException
    44This is a non checked exception.
    55 * Advantage: less boilerplate code
    … …  
    1717
    1818For now only one exception is implemented (org.geonetwork.domain.ebxml.exception.GeoNetworkException). We can add and diversify more of course.
     19
     20Heikki: -1. When was option 1 chosen and by whom ?? In my opinion throwing !RuntimeExceptions as a default strategy for exception handling does not make any sense. Also I do not think that try-catch blocks 'dirty' the code. Throwing !RuntimeException is a bit like avoiding strong typing by using ony java.lang.Object as prameter type; or like the current practice in GeoNetwork not to model an object domain, but do everything with JDOM Elements. Also what will we do if a !RuntimeException occurs: let the JVM exit?? I think not; this means we'll catch them somewhere in any case.
     21