Correct. Originally we had the option to choose whether exceptions should be thrown or wheter the return values (usually boolean) indicate an error.
However as exceptions are much more flexible and in order to make the API cleaner we decided to drop the return values. This option definetly won't come back. But as you can see from the examples, it is not hard to work with exceptions and the code is well-structured. Regards Rainer > from: Francis De Brabandere [mailto:[email protected]] > to: [email protected] > re: Re: Check exceptions > > On 17 June 2012 22:24, Iñigo Martínez <[email protected]> wrote: > > Hello: > > > > Recently I have been checking 2.3.0 version and I have noticed that > > the signature of some methods have changed. Now they don't return the > > operation result anymore. > > > > I know that checked exceptions have been discussed before[0], but, are > > they going to be considered again ? > > In fact that discussion was not about checked or unchecked exceptions but > rather about the not throwing exceptions vs throwing exceptions. > > I'm not sure we want to go the path of checked exceptions. There are pro's > and con's of course but it's a big change and there is no real consensus > within > the java community. > > Cheers, > Francis > > > > > Best regards, > > > > [0]: > > http://mail-archives.apache.org/mod_mbox/empire- > user/201008.mbox/%3CAA > > [email protected]%3E
