net.esper.core
Class UpdateDispatchViewBlocking
java.lang.Object
net.esper.view.ViewSupport
net.esper.core.UpdateDispatchViewBase
net.esper.core.UpdateDispatchViewBlocking
- All Implemented Interfaces:
- Iterable<EventBean>, Dispatchable, EventCollection, View, Viewable
public class UpdateDispatchViewBlocking
- extends UpdateDispatchViewBase
Convenience view for dispatching view updates received from a parent view to update listeners
via the dispatch service.
Method Summary |
void |
update(EventBean[] newData,
EventBean[] oldData)
Notify that data has been added or removed from the Viewable parent. |
Methods inherited from class net.esper.view.ViewSupport |
addView, dumpChildViews, dumpUpdateParams, findDescendent, getParent, getViews, hasViews, removeView, setParent, updateChildren, updateChildren |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
UpdateDispatchViewBlocking
public UpdateDispatchViewBlocking(EPServiceProvider epServiceProvider,
EPStatement statement,
EPStatementListenerSet updateListeners,
DispatchService dispatchService,
long msecTimeout)
- Ctor.
- Parameters:
epServiceProvider
- - engine instance to supply to statement-aware listenersstatement
- - the statement instance to supply to statement-aware listenersupdateListeners
- - listeners to updatedispatchService
- - for performing the dispatchmsecTimeout
- - timeout for preserving dispatch order through blocking
update
public void update(EventBean[] newData,
EventBean[] oldData)
- Description copied from interface:
View
- Notify that data has been added or removed from the Viewable parent.
The last object in the newData array of objects would be the newest object added to the parent view.
The first object of the oldData array of objects would be the oldest object removed from the parent view.
If the call to update contains new (inserted) data, then the first argument will be a non-empty list and the
second will be empty. Similarly, if the call is a notification of deleted data, then the first argument will be
empty and the second will be non-empty. Either the newData or oldData will be non-null.
This method won't be called with both arguments being null, but either one could be null.
The same is true for zero-length arrays. Either newData or oldData will be non-empty.
If both are non-empty, then the update is a modification notification.
When update() is called on a view by the parent object, the data in newData will be in the collection of the
parent, and its data structures will be arranged to reflect that.
The data in oldData will not be in the parent's data structures, and any access to the parent will indicate that
that data is no longer there.
- Parameters:
newData
- is the new data that has been added to the parent viewoldData
- is the old data that has been removed from the parent view