net.esper.eql.named
Class NamedWindowOnExprBaseView

java.lang.Object
  extended by net.esper.view.ViewSupport
      extended by net.esper.eql.named.NamedWindowOnExprBaseView
All Implemented Interfaces:
Iterable<EventBean>, EventCollection, StatementStopCallback, View, Viewable
Direct Known Subclasses:
NamedWindowOnDeleteView, NamedWindowOnSelectView

public abstract class NamedWindowOnExprBaseView
extends ViewSupport
implements StatementStopCallback

View for the on-delete statement that handles removing events from a named window.


Field Summary
protected  EventType namedWindowEventType
          The event type of the events hosted in the named window.
protected  NamedWindowRootView rootView
          The root view accepting removals (old data).
 
Fields inherited from class net.esper.view.ViewSupport
parent
 
Constructor Summary
NamedWindowOnExprBaseView(StatementStopService statementStopService, LookupStrategy lookupStrategy, NamedWindowRootView rootView)
          Ctor.
 
Method Summary
abstract  void handleMatching(EventBean[] triggerEvents, EventBean[] matchingEvents)
          Implemented by on-trigger views to action on the combination of trigger and matching events in the named window.
 void statementStopped()
          Indicates statement stopped.
 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
 

Field Detail

namedWindowEventType

protected final EventType namedWindowEventType
The event type of the events hosted in the named window.


rootView

protected final NamedWindowRootView rootView
The root view accepting removals (old data).

Constructor Detail

NamedWindowOnExprBaseView

public NamedWindowOnExprBaseView(StatementStopService statementStopService,
                                 LookupStrategy lookupStrategy,
                                 NamedWindowRootView rootView)
Ctor.

Parameters:
statementStopService - for indicating a statement was stopped or destroyed for cleanup
lookupStrategy - for handling trigger events to determine deleted events
rootView - to indicate which events to delete
Method Detail

handleMatching

public abstract void handleMatching(EventBean[] triggerEvents,
                                    EventBean[] matchingEvents)
Implemented by on-trigger views to action on the combination of trigger and matching events in the named window.

Parameters:
triggerEvents - is the trigger events (usually 1)
matchingEvents - is the matching events retrieved via lookup strategy

statementStopped

public void statementStopped()
Description copied from interface: StatementStopCallback
Indicates statement stopped.

Specified by:
statementStopped in interface StatementStopCallback

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.

Specified by:
update in interface View
Parameters:
newData - is the new data that has been added to the parent view
oldData - is the old data that has been removed from the parent view

© 2007 EsperTech Inc.
All rights reserved.
Visit us at espertech.com