Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have good number of Service and DAO classes which has the same set of 30 line exception code block which gets repeated and it shows up in Code Duplication report.

The approach which i can think of is to

  • Extract the common exception code block to a common method and call
    the method in one shot

    Re-organize the methods to ensure there is always one entry and exit point to Services or DAOs which will have just one set of exception code.

Are there any better ways to approach this scenario?

share|improve this question
please post a snippet of code as an example of what these blocks typically contain – gnat Jan 28 '13 at 13:14
I don't think you can do any better. Scala allows you to abstract over exception handlers (basically, an exception handler is just an object which conforms to a specific interface, so you can create an object with the semantics you want and just pass it as a handler anywhere you need those semantics), but AFAIK Java doesn't have anything similar. – Jörg W Mittag Jan 28 '13 at 13:30

Extract the exception handling into a method:

public interface Action {
    public void execute() throws ...;

public static void handleErrors(Action action) throws ... {
   try {
      // setup .....
   } catch (...) {
      // ...
   } finally {
      // cleanup ...

Then call it like this:

handleErrors(new Action(){ public void execute() throws ... {
    // ...

The syntax is ugly, but it's still much better than duplicating the error handling dozens of times. Anytime you are duplicating more than a couple of lines, you should stop and figure out how to avoid that duplication. In Java, this often means using interfaces and anonymous classes to pass one block of code to run inside some common control logic. The same technique can be reused to eliminate duplicated looping code.

share|improve this answer
lack of delegates really adds bloat in this example. Not trying to start trouble; just documenting the fact that while this is the best solution, it's a bit more natural in other languages. – brian Feb 5 '13 at 18:05
@brian: yes, this is easier in almost every other modern programming language. – kevin cline Feb 5 '13 at 23:48

Consider building an explicit exception handler.

It's a similar approach as your first suggestion but places the methods within an object instead. It's also similar to older, monolithic applications that had dedicated interrupt handlers. Either way, the point is the same - write the handling code once and then call as needed.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.