Eating exceptions in activate() methods?

[Bertrand Delacretaz]

The diffs of my revision 612808 changes include this, in
SimpleWebDavServlet.activate():

       try {
-            httpService.registerServlet(context, this, initparams, null);
-
-            // set the contextPath field to signal successfull registration
-            this.contextPath = context;
-
-        } catch (NamespaceException ne) {
-            // context collision
-
-        } catch (ServletException se) {
-            // servlet initialization failure
-
-        }

+          // Register servlet, and set the contextPath field to
signal successful registration
+          httpService.registerServlet(context, this, initparams, null);
+          this.contextPath = context;

Was there any reason to eat these exceptions?

To me it seems better to let the framework know that something went wrong.

-Bertrand