Avoid coupling the sender of a request to the receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along the chain until an object handles it.

The main intention in Chain Of Responsibility is to decouple the origin of the request and the handling of the request such that the origin of the request need not worry who and how its request is being handled as long as it gets the expected outcome. By decoupling the origin of the request and the request handler we make sure that both can change easily and new request handlers can be added without the origin of the request i.e client being aware of the changes. In this pattern we create a chain of objects such that each object will have a reference to another object which we call it as successor and these objects are responsible for handling the request from the client. All the objects which are part of the chain are created from classes which confirm to a common interface there by the client only needs to be aware of the interface and not necessarily the types of its implementations. The client assigns the request to first object part of the chain and the chain is created in such a way that there would be atleast one object which can handle the request or the client would be made aware of the fact that its request couldn’t be handled.

With this brief introduction I would like to put forth a very simple example to illustrate this pattern. In this example we create a chain of file parsers such that depending on the format of the file being passed to the parser, the parser has to decide whether its going to parse the file or pass the request to its successor parser to take action. The parser we would chain are: Simple text file parser, JSON file parser, CSV file parser and XML file parser. The parsing logic in each of these parser doesn’t parse any file, instead it just prints out a message stating who is handing the request for which file. We then populate file names of different formats into a list and then iterate through them passing the file name to the first parser in the list.

Lets define the Parser class, first let me show the class diagram for Parser class:

The Java code for the same is:

01 public class Parser {
02    
03   private Parser successor;
04    
05   public void parse(String fileName){
06     if ( getSuccessor() != null ){
07       getSuccessor().parse(fileName);
08     }
09     else{
10       System.out.println('Unable to find the correct parser for the file: '+fileName);
11     }
12   }
13    
14   protected boolean canHandleFile(String fileName, String format){
15     return (fileName == null) || (fileName.endsWith(format));
16          
17   }
18  
19   Parser getSuccessor() {
20     return successor;
21   }
22  
23   void setSuccessor(Parser successor) {
24     this.successor = successor;
25   }
26 }

We would now create different handlers for parsing different file formats namely- Simple text file, JSON file, CSV file, XML file and these extend from the Parser class and override the parse method. I have kept the implementation of different parser simple and these methods evaluate if the file has the format they are looking for. If a particular handler is unable to process the request i.e. the file format is not what it is looking for then the parent method handles such requests. The handler method in the parent class just invokes the same method on the successor handler.

The simple text parser:

01 public class TextParser extends Parser{
02  
03   public TextParser(Parser successor){
04     this.setSuccessor(successor);
05   }
06    
07   @Override
08   public void parse(String fileName) {
09     if ( canHandleFile(fileName, '.txt')){
10       System.out.println('A text parser is handling the file: '+fileName);
11     }
12     else{
13       super.parse(fileName);
14     }
15      
16   }
17  
18 }

The JSON parser:

01 public class JsonParser extends Parser {
02  
03   public JsonParser(Parser successor){
04     this.setSuccessor(successor);
05   }
06    
07   @Override
08   public void parse(String fileName) {
09     if ( canHandleFile(fileName, '.json')){
10       System.out.println('A JSON parser is handling the file: '+fileName);
11     }
12     else{
13       super.parse(fileName);
14     }
15  
16   }
17  
18 }

The CSV parser:

01 public class CsvParser extends Parser {
02  
03   public CsvParser(Parser successor){
04     this.setSuccessor(successor);
05   }
06    
07   @Override
08   public void parse(String fileName) {
09     if ( canHandleFile(fileName, '.csv')){
10       System.out.println('A CSV parser is handling the file: '+fileName);
11     }
12     else{
13       super.parse(fileName);
14     }
15   }
16  
17 }

The XML parser:

01 public class XmlParser extends Parser {
02    
03   @Override
04   public void parse(String fileName) {
05     if ( canHandleFile(fileName, '.xml')){
06       System.out.println('A XML parser is handling the file: '+fileName);
07     }
08     else{
09       super.parse(fileName);
10     }
11   }
12  
13 }

Now that we have all the handlers setup, we need to create a chain of handlers. In this example the chain we create is: TextParser -> JsonParser -> CsvParser -> XmlParser. And if XmlParser is unable to handle the request then the Parser class throws out a message stating that the request was not handled. Lets see the code for the client class which creates a list of files names and then creates the chain which I just described.

01 import java.util.List;
02 import java.util.ArrayList;
03  
04 public class ChainOfResponsibilityDemo {
05  
06   /**
07    * @param args
08    */
09   public static void main(String[] args) {
10      
11     //List of file names to parse.
12     List<String> fileList = populateFiles();
13      
14     //No successor for this handler because this is the last in chain.
15     Parser xmlParser = new XmlParser();
16  
17     //XmlParser is the successor of CsvParser.
18     Parser csvParser = new CsvParser(xmlParser);
19      
20     //CsvParser is the successor of JsonParser.
21     Parser jsonParser = new JsonParser(csvParser);
22      
23     //JsonParser is the successor of TextParser.
24     //TextParser is the start of the chain.
25     Parser textParser = new TextParser(jsonParser);
26      
27     //Pass the file name to the first handler in the chain.
28     for ( String fileName : fileList){
29       textParser.parse(fileName);
30     }
31  
32   }
33    
34   private static List<String> populateFiles(){
35      
36     List<String> fileList = new ArrayList<>();
37     fileList.add('someFile.txt');
38     fileList.add('otherFile.json');
39     fileList.add('xmlFile.xml');
40     fileList.add('csvFile.csv');
41     fileList.add('csvFile.doc');
42      
43     return fileList;
44   }
45  
46 }

In the file name list above I have intentionally added a file name for which there is no handler created. Running the above code gives us the output:

1 A text parser is handling the file: someFile.txt
2 A JSON parser is handling the file: otherFile.json
3 A XML parser is handling the file: xmlFile.xml
4 A CSV parser is handling the file: csvFile.csv
5 Unable to find the correct parser for the file: csvFile.doc

Happy coding and don’t forget to share!

Reference: Simple example to illustrate Chain Of Responsibility Design Pattern from our JCG partner Mohamed Sanaulla at the Experiences Unlimited blog.

Chain Of Responsibility Design Pattern Example的更多相关文章

  1. Design Patterns Uncovered: The Chain Of Responsibility Pattern

    Chain of Responsibility in the Real World The idea of the Chain Of Responsibility is that it avoids ...

  2. 深入浅出设计模式——职责链模式(Chain of Responsibility Pattern)

    模式动机 职责链可以是一条直线.一个环或者一个树形结构,最常见的职责链是直线型,即沿着一条单向的链来传递请求.链上的每一个对象都是请求处理者,职责链模式可以将请求的处理者组织成一条链,并使请求沿着链传 ...

  3. 二十四种设计模式:责任链模式(Chain of Responsibility Pattern)

    责任链模式(Chain of Responsibility Pattern) 介绍为解除请求的发送者和接收者之间耦合,而使多个对象都有机会处理这个请求.将这些对象连成一条链,并沿着这条链传递该请求,直 ...

  4. 乐在其中设计模式(C#) - 责任链模式(Chain of Responsibility Pattern)

    原文:乐在其中设计模式(C#) - 责任链模式(Chain of Responsibility Pattern) [索引页][源码下载] 乐在其中设计模式(C#) - 责任链模式(Chain of R ...

  5. C#设计模式之二十一职责链模式(Chain of Responsibility Pattern)【行为型】

    一.引言   今天我们开始讲"行为型"设计模式的第八个模式,该模式是[职责链模式],英文名称是:Chain of Responsibility Pattern.让我们看看现实生活中 ...

  6. 责任链模式 职责链模式 Chain of Responsibility Pattern 行为型 设计模式(十七)

    责任链模式(Chain of Responsibility Pattern) 职责链模式 意图 使多个对象都有机会处理请求,从而避免请求的发送者和接受者之间的耦合关系 将这些对象连接成一条链,并沿着这 ...

  7. C#设计模式之二十职责链模式(Chain of Responsibility Pattern)【行为型】

    一.引言 今天我们开始讲“行为型”设计模式的第八个模式,该模式是[职责链模式],英文名称是:Chain of Responsibility Pattern.让我们看看现实生活中的例子吧,理解起来可能更 ...

  8. 19.职责链模式(Chain of Responsibility Pattern)

    19.职责链模式(Chain of Responsibility Pattern)

  9. Chain of Responsibility Pattern

    1.Chain of Responsibility模式:将可能处理一个请求的对象链接成一个链,并将请求在这个链上传递,直到有对象处理该请求(可能需要提供一个默认处理所有请求的类,例如MFC中的Cwin ...

随机推荐

  1. js的拼接

    var datatr = " <tr>"; datatr += "<td bgcolor='#EEEEEE'><input class='i ...

  2. OGNL遍历list、map的常用三种方法

    package com.mylife.po; public class User { private String uname; private String pwd; public String g ...

  3. 黄聪:WordPress 多站点建站教程(三):主站如何调用子站的文章内容、SQL语句如何写?

    1.如果懂得编程的朋友可以SQL语句,然后加上PHP函数等操作就可以通过直接调用网站的数据库信息来实现想要达到的目的. 既然要用到SQL语句首先得对WordPress多站点数据库有一个了解,多站点激活 ...

  4. Java 利用缓冲字节流来实现视频、音频、图片的复制粘贴

    InputStream:继承自InputStream的流都是用于向程序中输入数据的,且数据单位都是字节(8位). OutputSteam:继承自OutputStream的流都是程序用于向外输出数据的, ...

  5. RouterOS SOCKS代理服务器(官方文档翻译)

    SOCKS 是基于TCP应用层协议穿透防火墙的代理服务器,即使防火墙阻止了一些应用端口,也能通过SOCKS代理穿透.SOCKS协议是独立于应用层的,因此可以用于WWW.FTP.Telnet等等. 来至 ...

  6. Hive插入数据的几种常用方法

    Hive的几种常见的数据导入方式这里介绍四种:(1).从本地文件系统中导入数据到Hive表:(2).从HDFS上导入数据到Hive表:(3).从别的表中查询出相应的数据并导入到Hive表中:(4).在 ...

  7. java中一个简单的下载示例

    首先在tomcat服务器下的webapps的download项目下建一个doc文件夹,再建个test.doc.防止控指针异常 DownLoad.java代码 package com.down; imp ...

  8. -bash: /usr/bin/yum: /usr/bin/python: bad interpreter: No such file or directory

    -bash: /usr/bin/yum: /usr/bin/python: bad interpreter: No such file or directory python多版本造成额问题 找不到p ...

  9. BTM事务配置

    请参考原贴:http://thinkdifferent.iteye.com/blog/1450433 Tomcat6上配置BTM 博客分类: practice tomcatjava )去http:// ...

  10. Tessnet2 a .NET 2.0 Open Source OCR assembly using Tesseract engine

    http://www.pixel-technology.com/freeware/tessnet2/ Tessnet2 a .NET 2.0 Open Source OCR assembly usin ...