Re: AW: [geclipse-dev] GridModelException

[Ariel Garcia <garcia@xxxxxxxxxx>]

> So as far as I remember the AuthenticationException is the only
> exception left besides ProblemException, right?! Any plans on removing
> this one?

i didn't look in detail how AuthenticationException  is being used, but for 
sure it is currently also a wrapper of ProblemException with the same 
constructors, and it appears only ~250 times instead of 850.... :-))
So removing that one should be much easier.

Anyways, the only advantage of keeping it would be if we are catching 
exceptions in a differentiated way at some places, ie,

   try {  ...  }
   catch ( AuthenticationException ae ) {
       do_something();
   } 
   // and we let other ProblemExceptions go trough

or we
   try {  ...  }
   catch ( AuthenticationException ae ) {
       do_something();
   } catch ( ProblemException pe ) {
       do_something_else();
   }

Otherwise we can always catch the PExc and check the type of problem it 
carries, but it might be more cumbersome. I will check the current uses...

Are there any dis/advantages you see?

Other opinions?

Cheers, Ariel