观察者模式中一般有两种,一种是推数据的模式(被观测对象向观测对象 送出数据,即在被观测对象发生改变时,主动告知被观测对象),一种是拉模式(观测对象主动去被观测对象去查询是否发生了变化)。虽然方式略有不同,但是基本上实现的原理是相似的。
从java提供的观察者模式的实现入手很容易理解。java提供了一个Observable基类和一个Observer接口,分别是被观测对象基类和观察者需要实现的接口。
简要分析这两个类:1 被观察者对象基类,此基类为于java.util包中,下面贴源码看一下
写道
/**
* This class represents an observable object, or "data"
* in the model-view paradigm. It can be subclassed to represent an
* object that the application wants to have observed.
* <p>
* An observable object can have one or more observers. An observer
* may be any object that implements interface <tt>Observer</tt>. After an
* observable instance changes, an application calling the
* <code>Observable</code>'s <code>notifyObservers</code> method
* causes all of its observers to be notified of the change by a call
* to their <code>update</code> method.
* <p>
* The order in which notifications will be delivered is unspecified.
* The default implementation provided in the Observable class will
* notify Observers in the order in which they registered interest, but
* subclasses may change this order, use no guaranteed order, deliver
* notifications on separate threads, or may guarantee that their
* subclass follows this order, as they choose.
* <p>
* Note that this notification mechanism is has nothing to do with threads
* and is completely separate from the <tt>wait</tt> and <tt>notify</tt>
* mechanism of class <tt>Object</tt>.
* <p>
* When an observable object is newly created, its set of observers is
* empty. Two observers are considered the same if and only if the
* <tt>equals</tt> method returns true for them.
*
* @author Chris Warth
* @version 1.39, 11/17/05
* @see java.util.Observable#notifyObservers()
* @see java.util.Observable#notifyObservers(java.lang.Object)
* @see java.util.Observer
* @see java.util.Observer#update(java.util.Observable, java.lang.Object)
* @since JDK1.0
*/
public class Observable {
private boolean changed = false;
private Vector obs;
/** Construct an Observable with zero Observers. */
public Observable() {
obs = new Vector();
}
/**
* Adds an observer to the set of observers for this object, provided
* that it is not the same as some observer already in the set.
* The order in which notifications will be delivered to multiple
* observers is not specified. See the class comment.
*
* @param o an observer to be added.
* @throws NullPointerException if the parameter o is null.
*/
public synchronized void addObserver(Observer o) {
if (o == null)
throw new NullPointerException();
if (!obs.contains(o)) {
obs.addElement(o);
}
}
/**
* Deletes an observer from the set of observers of this object.
* Passing <CODE>null</CODE> to this method will have no effect.
* @param o the observer to be deleted.
*/
public synchronized void deleteObserver(Observer o) {
obs.removeElement(o);
}
/**
* If this object has changed, as indicated by the
* <code>hasChanged</code> method, then notify all of its observers
* and then call the <code>clearChanged</code> method to
* indicate that this object has no longer changed.
* <p>
* Each observer has its <code>update</code> method called with two
* arguments: this observable object and <code>null</code>. In other
* words, this method is equivalent to:
* <blockquote><tt>
* notifyObservers(null)</tt></blockquote>
*
* @see java.util.Observable#clearChanged()
* @see java.util.Observable#hasChanged()
* @see java.util.Observer#update(java.util.Observable, java.lang.Object)
*/
public void notifyObservers() {
notifyObservers(null);
}
/**
* If this object has changed, as indicated by the
* <code>hasChanged</code> method, then notify all of its observers
* and then call the <code>clearChanged</code> method to indicate
* that this object has no longer changed.
* <p>
* Each observer has its <code>update</code> method called with two
* arguments: this observable object and the <code>arg</code> argument.
*
* @param arg any object.
* @see java.util.Observable#clearChanged()
* @see java.util.Observable#hasChanged()
* @see java.util.Observer#update(java.util.Observable, java.lang.Object)
*/
public void notifyObservers(Object arg) {
/*
* a temporary array buffer, used as a snapshot of the state of
* current Observers.
*/
Object[] arrLocal;
synchronized (this) {
/* We don't want the Observer doing callbacks into
* arbitrary code while holding its own Monitor.
* The code where we extract each Observable from
* the Vector and store the state of the Observer
* needs synchronization, but notifying observers
* does not (should not). The worst result of any
* potential race-condition here is that:
* 1) a newly-added Observer will miss a
* notification in progress
* 2) a recently unregistered Observer will be
* wrongly notified when it doesn't care
*/
if (!changed)
return;
arrLocal = obs.toArray();
clearChanged();
}
for (int i = arrLocal.length-1; i>=0; i--)
((Observer)arrLocal[i]).update(this, arg);
}
/**
* Clears the observer list so that this object no longer has any observers.
*/
public synchronized void deleteObservers() {
obs.removeAllElements();
}
/**
* Marks this <tt>Observable</tt> object as having been changed; the
* <tt>hasChanged</tt> method will now return <tt>true</tt>.
*/
protected synchronized void setChanged() {
changed = true;
}
/**
* Indicates that this object has no longer changed, or that it has
* already notified all of its observers of its most recent change,
* so that the <tt>hasChanged</tt> method will now return <tt>false</tt>.
* This method is called automatically by the
* <code>notifyObservers</code> methods.
*
* @see java.util.Observable#notifyObservers()
* @see java.util.Observable#notifyObservers(java.lang.Object)
*/
protected synchronized void clearChanged() {
changed = false;
}
/**
* Tests if this object has changed.
*
* @return <code>true</code> if and only if the <code>setChanged</code>
* method has been called more recently than the
* <code>clearChanged</code> method on this object;
* <code>false</code> otherwise.
* @see java.util.Observable#clearChanged()
* @see java.util.Observable#setChanged()
*/
public synchronized boolean hasChanged() {
return changed;
}
/**
* Returns the number of observers of this <tt>Observable</tt> object.
*
* @return the number of observers of this object.
*/
public synchronized int countObservers() {
return obs.size();
}
}
可以看出事实上,基类维护了一个同步的Vector来存放观察者,相关的提供了添加和删除观察者的方法,以及维护集合顺序之类的操作,这个基类中核心的方法就是notifyObservers(args),此方法调用观察者的公共接口update()方法。下面看一下观察者的接口 Observer ,此接口也位于java.util包下
/*
* @(#)Observer.java 1.20 05/11/17
*
* Copyright 2006 Sun Microsystems, Inc. All rights reserved.
* SUN PROPRIETARY/CONFIDENTIAL. Use is subject to license terms.
*/
package java.util;
/**
* A class can implement the <code>Observer</code> interface when it
* wants to be informed of changes in observable objects.
*
* @author Chris Warth
* @version 1.20, 11/17/05
* @see java.util.Observable
* @since JDK1.0
*/
public interface Observer {
/**
* This method is called whenever the observed object is changed. An
* application calls an <tt>Observable</tt> object's
* <code>notifyObservers</code> method to have all the object's
* observers notified of the change.
*
* @param o the observable object.
* @param arg an argument passed to the <code>notifyObservers</code>
* method.
*/
void update(Observable o, Object arg);
}
通过阅读这两个方法我们很容易理解观察者模式了。事实上就是莫中意义上的回调方法,当自己改变时通知关注此改变的监听者改变。
下面是一些demo示例
首先看被观察对象:
写道
public class ResourceBean extends Observable{
private String event;
//做点什么呢
public void doSomething(String event){
this.event= event;
setChanged();
System.out.println( "in resource bean event:"+event+" has done");
notifyObservers(event);
}
}
接下来看两个观察者
public class LockOberver implements Observer {
private static String INTREEST ="lock";
/* (non-Javadoc)
* @see java.util.Observer#update(java.util.Observable, java.lang.Object)
*/
@Override
public void update(Observable o, Object arg) {
if(INTREEST.equalsIgnoreCase( (String) arg)){
System.out.println("收到锁定的通知 "+o.toString()+ "变化值:"+ arg.toString());
}
}
}
public class UnlockOberver implements Observer {
private static String INTREEST ="unlock";
/* (non-Javadoc)
* @see java.util.Observer#update(java.util.Observable, java.lang.Object)
*/
@Override
public void update(Observable o, Object arg) {
if(INTREEST.equalsIgnoreCase( (String) arg)){
System.out.println("输出收到解锁的通知:"+o.toString()+" 参数值:"+arg.toString());
}
}
}
最后看一下如何 运行的示例
public class TestObserverPattern {
public static void main(String[] args){
ResourceBean bean = new ResourceBean();//被观测对象
LockOberver lock = new LockOberver();
UnlockOberver unlock = new UnlockOberver();
bean.addObserver(lock);
bean.addObserver(unlock);
bean.doSomething("lock");
bean.doSomething("freeAccess");
bean.doSomething("unlock");
}
}
运行的结果:
写道
in resource bean event:lock has done
收到锁定的通知 com.yasouth.ResourceBean@4a5ab2变化值:lock
in resource bean event:freeAccess has done
in resource bean event:unlock has done
输出收到解锁的通知:com.yasouth.ResourceBean@4a5ab2 参数值:unlock
这样一个简单的观察者示例就结束了
后续的工作是想了解一下,观察者模式中在java同步机制的具体应用,待续
分享到:
相关推荐
观察者模式,也被称为发布-订阅(Publish-Subscribe)模式,是软件设计模式中的行为模式之一。它定义了对象之间的一对多依赖关系,当一个对象的状态发生改变时,所有依赖于它的对象都会得到通知并自动更新。这种模式...
在“DesignPattern_ObserverPattern”文件中,我们可以看到一个完整的iOS观察者模式示例,包括创建主题、注册观察者、发布通知以及处理通知的方法。通过查看这个Demo,你可以了解到如何在实际项目中应用观察者模式,...
观察者模式是一种设计模式,属于行为模式类别,它在软件工程中被广泛应用于实现对象之间的松耦合。这种模式允许一个对象(称为"主题"或"被观察者")维护一个观察者列表,并在状态发生改变时通知这些观察者。在Java、...
在这个示例中,我们将深入探讨如何在Android Studio中使用Kotlin实现基于`java.util.*`的观察者模式。 首先,让我们理解观察者模式的核心概念。在Java的`java.util.Observable`类中,被观察者对象可以存储多个观察...
观察者模式(Observer Pattern)是设计模式中的一种行为模式,它定义了对象之间的一对多依赖关系,当一个对象的状态发生改变时,所有依赖于它的对象都会得到通知并被自动更新。这种模式常用于事件驱动的系统或者需要...
观察者模式 概述 定义对象间的一种一对多的依赖关系,当一个对象的状态发生改变时,所有依赖于它的对象都得到通知并被自动更新。 适用性 1.当一个抽象模型有两个方面,其中一个方面依赖于另一方面。 将这二者封装...
在这个"observer-pattern-demo"的示例中,我们将深入探讨观察者模式的原理、结构和应用场景。 **1. 模式定义** 观察者模式定义了对象之间的一对多依赖关系,当一个对象的状态发生改变时,所有依赖于它的对象都会...
观察者模式是软件设计模式中的一种行为模式,它允许一个对象,称为"主题",维护一个依赖于它的对象列表,这些对象被称为"观察者"。当主题的状态发生改变时,它会通知所有观察者,使它们能够自动更新自己。这种模式在...
1. 发布订阅/观察者模型,实现业务之间的解耦。 2.比如新增用户完成需要发短信、记录日志等,这些逻辑堆在新增方法的最后面实在不太合理,而且不易复用。 3.对解耦代码有很大的帮助,比如多种业务场景做完都要插入...
下面是一个简化的观察者模式示例: ```java public class WeatherData extends Observable { private float temperature, humidity, pressure; public void measurementsChanged() { setChanged(); ...
Java 观察者模式示例代码: ```java import java.util.ArrayList; import java.util.List; // 抽象主题接口 interface Subject { void registerObserver(Observer observer); void removeObserver(Observer ...
以下是一个简单的观察者模式示例: ```java import java.util.*; // 被观察者(主题)接口 interface Subject { void registerObserver(Observer observer); void removeObserver(Observer observer); void ...
#### 三、观察者模式示例 下面通过两个具体的示例来说明如何在JavaScript中实现观察者模式。 **示例1:** 在这个例子中,我们创建了一个简单的弹出窗口(子窗口),该窗口可以从打开它的父窗口接收数据,并在用户...
总的来说,这个压缩包提供了一个C++实现的观察者模式示例,适用于学习和理解设计模式。通过分析和运行这些源代码,你可以更深入地了解如何在实际项目中应用观察者模式来处理对象间的通信和状态同步问题。同时,这个...
在本示例中,PHP观察者模式通过以下几个关键部分来实现: 1. 抽象主题类(Subject):这是一个接口,定义了观察者模式中的主题行为。它规定了主题必须具备的方法,包括附加(attach)、分离(detach)和通知...
公共交通监视 观察者模式示例 规格 公交车司机可能会延迟到达的时间。 然后,公共交通监视系统将这些信息传递给所有订户/观察员 班级
在这个程序示例中,结合了事件风格和观察者模式,这两种设计模式在软件工程中都扮演着重要的角色。 **事件风格编程** 是一种编程范式,它将程序设计为对特定事件的响应。在事件驱动的系统中,程序的执行不依赖于...
本文将深入探讨如何使用SPL实现观察者模式,并通过一个具体的登录处理示例进行说明。 首先,我们需要了解SPL中的两个关键角色:`SplSubject` 和 `SplObserver` 接口。`SplSubject` 是被观察的对象,而 `SplObserver...