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:
03 |
private Parser successor; |
05 |
public void parse(String fileName){ |
06 |
if ( getSuccessor() != null ){ |
07 |
getSuccessor().parse(fileName); |
10 |
System.out.println('Unable to find the correct parser for the file: '+fileName); |
14 |
protected boolean canHandleFile(String fileName, String format){ |
15 |
return (fileName == null) || (fileName.endsWith(format)); |
19 |
Parser getSuccessor() { |
23 |
void setSuccessor(Parser successor) { |
24 |
this.successor = successor; |
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{ |
03 |
public TextParser(Parser successor){ |
04 |
this.setSuccessor(successor); |
08 |
public void parse(String fileName) { |
09 |
if ( canHandleFile(fileName, '.txt')){ |
10 |
System.out.println('A text parser is handling the file: '+fileName); |
13 |
super.parse(fileName); |
The JSON parser:
01 |
public class JsonParser extends Parser { |
03 |
public JsonParser(Parser successor){ |
04 |
this.setSuccessor(successor); |
08 |
public void parse(String fileName) { |
09 |
if ( canHandleFile(fileName, '.json')){ |
10 |
System.out.println('A JSON parser is handling the file: '+fileName); |
13 |
super.parse(fileName); |
The CSV parser:
01 |
public class CsvParser extends Parser { |
03 |
public CsvParser(Parser successor){ |
04 |
this.setSuccessor(successor); |
08 |
public void parse(String fileName) { |
09 |
if ( canHandleFile(fileName, '.csv')){ |
10 |
System.out.println('A CSV parser is handling the file: '+fileName); |
13 |
super.parse(fileName); |
The XML parser:
01 |
public class XmlParser extends Parser { |
04 |
public void parse(String fileName) { |
05 |
if ( canHandleFile(fileName, '.xml')){ |
06 |
System.out.println('A XML parser is handling the file: '+fileName); |
09 |
super.parse(fileName); |
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; |
04 |
public class ChainOfResponsibilityDemo { |
09 |
public static void main(String[] args) { |
11 |
//List of file names to parse. |
12 |
List<String> fileList = populateFiles(); |
14 |
//No successor for this handler because this is the last in chain. |
15 |
Parser xmlParser = new XmlParser(); |
17 |
//XmlParser is the successor of CsvParser. |
18 |
Parser csvParser = new CsvParser(xmlParser); |
20 |
//CsvParser is the successor of JsonParser. |
21 |
Parser jsonParser = new JsonParser(csvParser); |
23 |
//JsonParser is the successor of TextParser. |
24 |
//TextParser is the start of the chain. |
25 |
Parser textParser = new TextParser(jsonParser); |
27 |
//Pass the file name to the first handler in the chain. |
28 |
for ( String fileName : fileList){ |
29 |
textParser.parse(fileName); |
34 |
private static List<String> populateFiles(){ |
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'); |
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.
- 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 ...
- 深入浅出设计模式——职责链模式(Chain of Responsibility Pattern)
模式动机 职责链可以是一条直线.一个环或者一个树形结构,最常见的职责链是直线型,即沿着一条单向的链来传递请求.链上的每一个对象都是请求处理者,职责链模式可以将请求的处理者组织成一条链,并使请求沿着链传 ...
- 二十四种设计模式:责任链模式(Chain of Responsibility Pattern)
责任链模式(Chain of Responsibility Pattern) 介绍为解除请求的发送者和接收者之间耦合,而使多个对象都有机会处理这个请求.将这些对象连成一条链,并沿着这条链传递该请求,直 ...
- 乐在其中设计模式(C#) - 责任链模式(Chain of Responsibility Pattern)
原文:乐在其中设计模式(C#) - 责任链模式(Chain of Responsibility Pattern) [索引页][源码下载] 乐在其中设计模式(C#) - 责任链模式(Chain of R ...
- C#设计模式之二十一职责链模式(Chain of Responsibility Pattern)【行为型】
一.引言 今天我们开始讲"行为型"设计模式的第八个模式,该模式是[职责链模式],英文名称是:Chain of Responsibility Pattern.让我们看看现实生活中 ...
- 责任链模式 职责链模式 Chain of Responsibility Pattern 行为型 设计模式(十七)
责任链模式(Chain of Responsibility Pattern) 职责链模式 意图 使多个对象都有机会处理请求,从而避免请求的发送者和接受者之间的耦合关系 将这些对象连接成一条链,并沿着这 ...
- C#设计模式之二十职责链模式(Chain of Responsibility Pattern)【行为型】
一.引言 今天我们开始讲“行为型”设计模式的第八个模式,该模式是[职责链模式],英文名称是:Chain of Responsibility Pattern.让我们看看现实生活中的例子吧,理解起来可能更 ...
- 19.职责链模式(Chain of Responsibility Pattern)
19.职责链模式(Chain of Responsibility Pattern)
- Chain of Responsibility Pattern
1.Chain of Responsibility模式:将可能处理一个请求的对象链接成一个链,并将请求在这个链上传递,直到有对象处理该请求(可能需要提供一个默认处理所有请求的类,例如MFC中的Cwin ...
- Form中的keypress事件不能用
Form中的keypress事件不能用 编写人:CC阿爸 2015-4-8 近期在修改系统时,想给一画面增加一个组合键功能,但在form_keypress事件中加入代码,但无论如何也不能触发该动作. ...
- HDU 2201 熊猫阿波的故事
熊猫阿波的故事 Time Limit: 1000/1000 MS (Java/Others) Memory Limit: 32768/32768 K (Java/Others)Total Sub ...
- MVVMLight介绍以及在项目中的使用
http://www.des8.me/detail-1822826.html 一.MVVM 和 MVVMLight介绍 MVVM是Model-View-ViewModel的简写.类似于目前比较流行的M ...
- oracle link的创建过程
下面做一个测试,在测试中,创建数据库链接的库为XJ(WINDOWS 2003 ORACLE 10g 10.2.0.1),被链接的库为DMDB(LINUX AS5 ORACLE 10g 10.2.0.1 ...
- pdf转换成可在线浏览的电子杂志zmaker_pdf
zmaker是曾经国内最流行的电子杂志制作软件,可惜可惜,不过幸好有人给发布了 最新版的 其实主要是2个流程 一个是软件的安装 软件的下载和安装请参考 官方教材 http://bbs.emaghome ...
- 如何优化Java垃圾回收-zz
为什么需要优化GC 或者说的更确切一些,对于基于Java的服务,是否有必要优化GC?应该说,对于所有的基于Java的服务,并不总是需要进行GC优化,但前提是所运行的基于Java的系统,包含了如下参数或 ...
- 一个检测网页是否有日常链接的python脚本
在大的互联网公司干技术的基本都会碰到测试.预发布.线上这种多套环境的,来实现测试和线上正式环境的隔离,这种情况下,就难免会碰到秀逗了把测试的链接发布到线上的情况,一般这种都是通过一些测试的检查工具来检 ...
- Spring Boot实践——基础和常用配置
借鉴:https://blog.csdn.net/j903829182/article/details/74906948 一.Spring Boot 启动注解说明 @SpringBootApplica ...
- @@ERROR和@@ROWCOUNT的用法
1. @ERROR 当前一个语句遇到错误,则返回错误号,否则返回0.需要注意的是@ERROR在每一条语句执行后会被立刻重置,因此应该在要验证的语句执行后检查数值或者是将它保存到局部变量 ...
- 迷你MVVM框架 avalonjs 0.91发布
本版本修了一些BUG与不合理的地方,感谢感谢ztz, 民工精髓, 姚立, qiangtou等人指正. 处理AMD加载 旧式IE下移除script节点内存泄漏的问题 fix firefox 全系列vis ...