Chain of Responsibility Design Pattern in Java

By -

Type : Behavioral Design Pattern

Summary


Chain of Responsibility deals with how best we can design a sender - receivers without tight coupling the sender and receivers. Where the sender
sends an object to a set of receivers. And one or more than one receiver work on the object that the sender sent.

Details

As the name suggests, rather than the Client deciding how to process an request object( Say by calling specific method from specific Object), the request is sent though a pipe or chain of different Objects which might be able to process the request.

The request enters from one end and pass on the request to the next Handler until the request processor is done.

Following are the participants in this pattern
Handler : An Interface that Concrete Handlers implements
Concrete Handler : Handler implementation that processes the request, or pass to the next handler in the chain.
Client : Client that utilizes the chain of handlers by invoking first handler.

Advantages

Sender and receiver (handler) can go independently
Follows plug in like architecture, where we can add more handler without changing existing behaviour.
Easy to maintenance and more testable code. 

Disadvantages

If the handlers are not implemented properly it could result in broken processing the request.
Based on the logic wrong order of the Handler in the chain could cause issue.

Example 

Let's take example of a software system which processes customer request. Broadly we have divided the customer request as of 3 types for now Account, Billing and Technical support related. When client sends the request we loop though all the respective handler and process the request. We also have a Default handler which works when the customer that is asking for something we donot support.

Class Diagram



Sample Code 



// interface to represent a request
public interface Request {

  public String [] getRequestDetails(); //PasswordReset, UnlockAccount, GetAccountDetails
  
  public void setRequestDetails(String [] news); //PasswordReset, UnlockAccount, GetAccountDetails
}

// customer support request object containging request details
public class CustomerSupportRequest implements Request {

  private String[] requestDetails;

  public CustomerSupportRequest(String[] reqType) {
    this.requestDetails = reqType;
  }

}

// abstract request handler
public abstract class RequestHandler {

  RequestHandler nextHandler;

  public void setNextHandler(RequestHandler handler) {
    this.nextHandler = handler;
  }

  public void handleRequest(Request req) {
    processRequest(req);
    if (this.nextHandler != null) {
      this.nextHandler.handleRequest(req);
    }
  }

  public abstract void processRequest(Request req);
  
}


// account related request handler
public class AccountRequestHandler extends RequestHandler {

  @Override
  public void processRequest(Request req) {
    System.out.println("ACCOUNT DEPARTMENT HANDLED!");
  }

}

//billing related request handler
public class BillingRequestHandler extends RequestHandler {

  @Override
  public void processRequest(Request req) {

    System.out.println("BILLING DEPARTMENT HANDLED!");

  }

}

//technical related request handler
public class TechnicalRequestHandler extends RequestHandler {

  @Override
  public void processRequest(Request req) {
   
    System.out.println("TECH DEPARTMENT HANDLED!");
    
  }

}

Comments

Post a Comment

Popular posts from this blog

Converting Java Map to String

By -
Java Collections framework, String manipulation etc is something that we often encounter in Development process. For processing collections (like checking null/empty, Intersection, Disjunction) We do have some of the very use full libraries. Some of the Collection related libraries are Apche Commons Collections and Google  Collections(Guava). Problem Use Case This article explains how to convert a Java Map to String(and vice versa) using different libraries and technique. One way is to use StringBuilder(Or String) and loop though the Map and build the String by applying some sort of separator ( for key:value and entry). Here we have to take care of the null value etc. Without Any Library If we want to convert the map to a String with key value separator and also individual entry seperator in the resulting String, we have to write code for that. For a simple Map, we have to iterate though the map, take care of the null values etc. Following is a sample to get String built
Read more

Difference between volatile and synchronized

By -
volatile is a field modifier, while synchronized modifies code blocks and methods. So we can specify three variations of a simple accessor using those two keywords: int i1; int geti1() {return i1;} volatile int i2; int geti2() {return i2;} int i3; synchronized int geti3() {return i3;} geti1() accesses the value currently stored in i1 in the current thread . Threads can have local copies of variables, and the data does not have to be the same as the data held in other threads. In particular, another thread may have updated i1 in it's thread, but the value in the current thread could be different from that updated value. In fact Java has the idea of a "main" memory, and this is the memory that holds the current "correct" value for variables. Threads can have their own copy of data for variables, and the thread copy can be different from the "main" memory. So in fact, it is possible for the "main"
Read more

Invoking EJB deployed on a remote machine

By -
Invoking EJB deployed on a remote machine In case we are calling remote ejb( ejb deployed on remote machines), The JNDI lookup might lookup like, Properties env = new Properties(); env.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory"); env.put(Context.PROVIDER_URL, "XX.XXX.XX.XX:1099"); env.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); Context ctx = new InitialContext(env); If we are calling local ejb then we can simply create InitialContext without any parameters. Like, Context ctx = new InitialContext();
Read more