I think that's what most of us do! Problem is, all those extra methods create noise at the class level - even if individual methods are comparatively clean.
@sneakyThrows or chuck can help out here. I personally prefer chuck as it's implemented completely within Java syntax and doesn't need annotations. (I'd still happily use Lombok for case classes though.) Of course, you need buy-in from the rest of your team to use other libraries like this, and if you can get that far then it's probably worth going all the way and trying to sell them on Scala... On 24 September 2010 14:26, Miroslav Pokorny <[email protected]>wrote: > Simply create a private method which does my work and throws all checked. > The original method is simply a try/catch and call to the helper. No noise > in the important method and alls well. Not a big deal. > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<javaposse%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > -- Kevin Wright mail / gtalk / msn : [email protected] pulse / skype: kev.lee.wright twitter: @thecoda -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
