中介者模式(Mediator Pattern)是一种行为设计模式,它定义了一组对象和一个用来与这组对象进行通信的中介对象。这组对象被称为同事(Colleague),而中介对象则被称为中介者(Mediator)。中介者模式的主要目的是降低各个同事类之间的耦合度,提高代码的可维护性和扩展性。
中介者模式的基本结构如下:
- 抽象中介者(Mediator):定义了一个接口,用于封装同事对象之间的所有交互。
- 具体中介者(ConcreteMediator):实现了抽象中介者接口,负责协调各个同事对象的交互。
- 抽象同事(Colleague):定义了一组接口,用于表示同事对象之间的交互。
- 具体同事(ConcreteColleague):实现了抽象同事接口,表示一个具体的同事对象。
下面我们通过一个简单的例子来详细介绍中介者模式。这个例子中,我们模拟了一个公司的请假审批过程,其中涉及到员工(Employee)、经理(Manager)和人事部门(HRDepartment)三个角色。
首先,我们定义一个抽象中介者接口Mediator
:
public interface Mediator {
void sendMessage(String message, Colleague recipient);
}
然后,我们定义一个抽象同事接口Colleague
:
public interface Colleague {
void setMediator(Mediator mediator);
String getMessage();
}
接下来,我们实现具体同事类。员工类(Employee)和经理类(Manager)都需要向人事部门(HRDepartment)发送请假申请,因此它们都需要持有一个Mediator
对象,并通过这个对象来发送消息。
public class Employee extends Colleague {
private String name;
private Mediator mediator;
public Employee(String name) {
this.name = name;
}
@Override
public void setMediator(Mediator mediator) {
this.mediator = mediator;
}
@Override
public String getMessage() {
return "Employee " + this.name + " wants to take a leave for " + this.leaveDays + " days.";
}
public void applyLeave(int leaveDays) {
this.leaveDays = leaveDays;
String message = getMessage();
mediator.sendMessage(message, this);
}
}
public class Manager extends Colleague {
private String name;
private Mediator mediator;
public Manager(String name) {
this.name = name;
}
@Override
public void setMediator(Mediator mediator) {
this.mediator = mediator;
}
@Override
public String getMessage() {
return "Manager " + this.name + " wants to approve the leave application for Employee.";
}
public void approve(Employee employee) {
String message = getMessage();
mediator.sendMessage(message, employee);
}
}
人事部门类(HRDepartment)需要接收并处理来自员工和经理的消息,因此它是一个具体中介者类:
public class HRDepartment extends Mediator {
@Override
public void sendMessage(String message, Colleague recipient) {
if (recipient instanceof Employee) {
System.out.println("HRDepartment received message: " + message);
System.out.println("Leave application approved by manager.");
} else if (recipient instanceof Manager) {
System.out.println("HRDepartment received message: " + message);
System.out.println("Leave application is waiting for manager's approval.");
}
}
}
最后,我们编写一个简单的测试程序来演示中介者模式的工作原理:
public class Test {
public static void main(String[] args) {
Mediator mediator = new HRDepartment();
Employee john = new Employee("John");
Employee jane = new Employee("Jane");
Manager tom = new Manager("Tom");
john.setMediator(mediator);
jane.setMediator(mediator);
tom.setMediator(mediator);
mediator.sendMessage(john.getMessage(), john);
mediator.sendMessage(tom.getMessage(), john);
mediator.sendMessage(jane.getMessage(), john);
}
}
运行上述测试程序,我们可以得到以下输出结果:
HRDepartment received message: Employee John wants to take a leave for 5 days.
Leave application is waiting for manager's approval.
HRDepartment received message: Employee Jane wants to take a leave for 7 days.
Leave application is waiting for manager's approval.
HRDepartment received message: Manager Tom wants to approve the leave application for Employee.
Leave application approved by manager.
Leave application approved by manager.
通过这个例子,我们可以看到中介者模式有效地降低了员工、经理和人事部门之间的耦合度,使得整个请假审批过程更加清晰和易于维护。当需要添加新的同事对象时,只需要在中介者类中添加相应的处理逻辑即可,无需修改其他同事类。