Changes between Version 7 and Version 8 of GeoNetworkException

Timestamp:

Dec 2, 2008, 2:44:23 AM (15 years ago)

Author:

heikki

Comment:

--

GeoNetworkException

@@ -13 +13 @@
 
 
-'''Chosen option 1 (disputed)''': 
-The application is well unit tested. It is important that the code remains clean. 
+'''Chosen option 2 (disputed)''': 
+In the ESA chat on December 1st 2008, option 2 was preferred by Heikki & Jose. Erik does not agree but accepts his is a minority position on this issue.
 
 For now only one exception is implemented (org.geonetwork.domain.ebxml.exception.GeoNetworkException). We can add and diversify more of course. 
@@ -21 +21 @@
   Generally speaking, do not throw a !RuntimeException or create a subclass of !RuntimeException simply because you don't want to be bothered with specifying the exceptions your methods can throw. 
 
-Erik: +1. Since I like the minimalistic approach I prefer 1. Another advantage is that you have always the choice to catch the exception. In this project does it mean that the exception will be catched in the service layer. In all other layers you don't see boilerplate code, only code which makes sense. 
+Erik: +1. The application is well unit tested. It is important that the code remains clean. Since I like the minimalistic approach I prefer 1. Another advantage is that you have always the choice to catch the exception. In this project does it mean that the exception will be catched in the service layer. In all other layers you don't see boilerplate code, only code which makes sense.