1、定义
(Chain of Responsibility)使多个对象都有机会处理请求,从而避免请求的发送者和接收者之间的耦合关系。将这个对象连成一条链,沿着这条链传递该请求,直到有一个对象处理它为止。
2、使用场景
一个普通职员,需要申请请假流程,部门经理能够审批1-3天类的请假,总监能审批4-6天的请假,总经理能审批7-14天的请假申请,同时总经理可以处理员工调薪等申请审批。
3、代码结构UML图
管理者:定义一个处理请求的接口;
部门经理、总监、总经理:具体处理者类,处理它所负责的请求,可访问它的后继者,如果可处理该请求,就处理之,否则就将该请求抓发给它的后继者。
4、类的实现
(1)、Manager(管理者类)
public abstract class Manager {
protected String name;
protected Manager superior;
public Manager(String name) {
this.name = name;
}
//设置管理者的上级
public void setSuperior(Manager superior){
this.superior=superior;
}
//申请请求
abstract public void requestApplications(Request request);
}
(2)、CommonManager (部门经理类)
public class CommonManager extends Manager {
public CommonManager(String name) {
super(name);
}
@Override
public void requestApplications(Request request) {
if ("请假".equals(request.getRequestType()) && request.getNumber() <= 3) {
System.out.println(name + ":" + request.getRequestContent() + "数量" + request.getNumber() + "被批准。");
} else {
if (null != superior) {
//其余的都转到上级
superior.requestApplications(request);
}
}
}
}
(3)、Majordomo (总监类)
public class Majordomo extends Manager {
public Majordomo(String name) {
super(name);
}
@Override
public void requestApplications(Request request) {
if ("请假".equals(request.getRequestType()) && request.getNumber() <= 6) {
System.out.println(name + ":" + request.getRequestContent() + "数量" + request.getNumber() + "被批准。");
} else {
if (null != superior) {
superior.requestApplications(request);
}
}
}
}
(4)、GeneralManager (总经理类)
public class GeneralManager extends Manager {
public GeneralManager(String name) {
super(name);
}
@Override
public void requestApplications(Request request) {
if ("请假".equals(request.getRequestType())) {
System.out.println(name + ":" + request.getRequestContent() + "数量" + request.getNumber() + "被批准。");
} else if ("加薪".equals(request.getRequestType()) && request.getNumber() <= 500) {
System.out.println(name + ":" + request.getRequestContent() + "数量" + request.getNumber() + "被批准。");
} else if ("加薪".equals(request.getRequestType()) && request.getNumber() > 500) {
System.out.println(name + ":" + request.getRequestContent() + "数量" + request.getNumber() + "再说吧。");
}
}
}
(5)、Request (发起申请类)
public class Request {
private String requestType;
private String requestContent;
private int number;
public String getRequestType() {
return requestType;
}
public void setRequestType(String requestType) {
this.requestType = requestType;
}
public String getRequestContent() {
return requestContent;
}
public void setRequestContent(String requestContent) {
this.requestContent = requestContent;
}
public int getNumber() {
return number;
}
public void setNumber(int number) {
this.number = number;
}
}
5、客户端调用
public static void main(String[] args) {
CommonManager bmjl=new CommonManager("部门经理");
Majordomo zj=new Majordomo("总监");
GeneralManager zjl=new GeneralManager("总经理");
//设置上级,可根据实际修改
bmjl.setSuperior(zj);
zj.setSuperior(zjl);
Request request=new Request();
request.setRequestType("请假");
request.setRequestContent("小明请假");
request.setNumber(1);
bmjl.requestApplications(request);
Request request2=new Request();
request2.setRequestType("请假");
request2.setRequestContent("小明请假");
request2.setNumber(4);
bmjl.requestApplications(request2);
Request request3=new Request();
request3.setRequestType("请假");
request3.setRequestContent("小明请假");
request3.setNumber(8);
bmjl.requestApplications(request3);
Request request4=new Request();
request4.setRequestType("加薪");
request4.setRequestContent("小明申请加薪");
request4.setNumber(400);
bmjl.requestApplications(request4);
Request request5=new Request();
request5.setRequestType("加薪");
request5.setRequestContent("小明申请加薪");
request5.setNumber(1000);
bmjl.requestApplications(request5);
}
输出:
6、总结
最关键的是,当客户提交一个请求时,请求是沿链传递直至有一个ConcreteHandler对象负责处理它。
接收者和发送者都没有对方的明确信息,且链中的对象自己也并不知道链的结构。结果是职责链可简化对象的相互连接,他们仅需要保持一个指向其后继者的引用,而不需保持它所有的候选接受者的引用。这也大大降低了耦合度了。
可以随时地添加或修改处理一个请求的结构,增强了给对象指派职责的灵活性,不过也需要当心,一个请求极有可能到了链的末端都得不到处理,或者因为没有正确配置而得不到处理,这就很糟糕,需要事先考虑全面。
参考:《大话设计模式》