1.定义:
用一个中介对象来封装一系列的对象交互。中介者使各对象不需要显式地相互引用,从而使其耦合松散,而且可以独立地改变它们之间的交互。(比如各国与联合国)
2.UML类图:
3.简单代码实现:
package com.guo.mediatorPattern;
public abstract class Mediator {
public abstract void send(String message,Colleague colleague);
}
package com.guo.mediatorPattern;
public abstract class Colleague {
protected Mediator mediator;
//抽象同事类,得到中介者对象
public Colleague(Mediator mediator) {
this.mediator = mediator;
}
}
package com.guo.mediatorPattern;
public class ConcreteColleague1 extends Colleague {
public ConcreteColleague1(Mediator mediator) {
super(mediator);
}
public void send(String message){
mediator.send(message, this);
}
public void notifyColleague(String message){
System.out.println("同事1得到消息:" + message);
}
}
package com.guo.mediatorPattern;
public class ConcreteColleague2 extends Colleague {
public ConcreteColleague2(Mediator mediator) {
super(mediator);
}
public void send(String message){
mediator.send(message, this);
}
public void notifyColleague(String message){
System.out.println("同事2得到消息:" + message);
}
}
package com.guo.mediatorPattern;
public class ConcreteMediator extends Mediator {
//具体的中介者需要知道所有的同事对象
private ConcreteColleague1 colleague1;
private ConcreteColleague2 colleague2;
public ConcreteColleague1 getColleague1() {
return colleague1;
}
public void setColleague1(ConcreteColleague1 colleague1) {
this.colleague1 = colleague1;
}
public ConcreteColleague2 getColleague2() {
return colleague2;
}
public void setColleague2(ConcreteColleague2 colleague2) {
this.colleague2 = colleague2;
}
@Override
public void send(String message, Colleague colleague) {
if (colleague == colleague1) {
colleague2.notifyColleague(message);
} else {
colleague1.notifyColleague(message);
}
}
}
//客户端代码
public static void main(String[] args) {
ConcreteMediator mediator = new ConcreteMediator();
ConcreteColleague1 concreteColleague1 = new ConcreteColleague1(mediator);
ConcreteColleague2 concreteColleague2 = new ConcreteColleague2(mediator);
mediator.setColleague1(concreteColleague1);
mediator.setColleague2(concreteColleague2);
concreteColleague1.send("你吃饭了么?");
concreteColleague2.send("没呢,你打算请客?");
}
4.优缺点:中介者模式很容易在系统中应用,也很容易在系统中误用。当系统出现了“多对多”交互复杂的对象群时,不要急于使用中介者模式,而要先反思你的系统在设计上是否合理。
优点:Mediator的出现减少了各个Colleague的耦合,使得可以独立地改变和复用各个Colleague类和Mediator。其次,由于把对象如何协作进行了抽象,将中介作为一个独立的概念并将其封装在一个对象中,这样关注的对象就从对象各自本身的行为转移到它们之间的交互上来,也就是站在一个更宏观的角度去看待系统。
缺点:由于ConcreteMediator控制了集中化,于是就把交互复杂性变为了中介者的复杂性,这就使得中介者会变得比任何一个ConcreteColleague都复杂。
5.使用场合:
一般应用于一组对象以定义良好但是复杂的方式进行通信的场合以及想定制一个分布在多个类中的行为,而又不想生成太多的子类的场合。