Checked exceptions throw a burden onto the developer. He is forced to do something. Why force this burden? It assumes something SHOULD be done for these particular errors. I don't think that's realistic (they're OS errors -- not business errors), which is why checked exceptions have fallen well out of favor in the last decade.
On Mon, Oct 25, 2010 at 12:48 PM, Filip Defoort <filip...@cirquedigital.com> wrote: > On Mon, Oct 25, 2010 at 10:45 AM, James Carman > <ja...@carmanconsulting.com> wrote: >> On Mon, Oct 25, 2010 at 1:41 PM, Filip Defoort >> <filip...@cirquedigital.com> wrote: >>> >>> Yes! Very much so. It's quite useful when dealing with stale nfs, >>> locked files,... >>> >> >> Do you implement the retry logic in every place where you need it or >> do you have a helper method that takes some sort of functor and it >> wraps it in the try/catch/retry logic? >> > > Depends. I do have a bunch of wrappers for common types of retries, > but often the remedy really is different depending on the operation > (I'm dealing a lot with search indexes, updating them and transaction > locking). > > - Filip > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
