public class TableOnMergeInsertUnmatched extends ViewSupport implements StopCallback, TableOnView
EMPTY_VIEW_ARRAY| Constructor and Description |
|---|
TableOnMergeInsertUnmatched(TableStateInstance tableStateInstance,
ExprEvaluatorContext exprEvaluatorContext,
TableMetadata metadata,
TableOnMergeViewFactory parent) |
| Modifier and Type | Method and Description |
|---|---|
EventType |
getEventType()
Provides metadata information about the type of object the event collection contains.
|
java.util.Iterator<EventBean> |
iterator()
Allows iteration through all elements in this event collection.
|
void |
stop()
Stops the underlying resources.
|
void |
update(EventBean[] newData,
EventBean[] oldData)
Notify that data has been added or removed from the Viewable parent.
|
addView, addView, dumpChildViews, dumpUpdateParams, dumpUpdateParams, findDescendent, findViewIndex, getParent, getViews, hasViews, removeAllViews, removeView, removeView, setParent, updateChildren, updateChildrenclone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, waitaddView, getViews, hasViews, removeAllViews, removeViewpublic TableOnMergeInsertUnmatched(TableStateInstance tableStateInstance, ExprEvaluatorContext exprEvaluatorContext, TableMetadata metadata, TableOnMergeViewFactory parent)
public void stop()
StopCallbackstop in interface StopCallbackpublic EventType getEventType()
EventCollectiongetEventType in interface EventCollectionpublic java.util.Iterator<EventBean> iterator()
EventCollectioniterator in interface EventCollectioniterator in interface java.lang.Iterable<EventBean>public void update(EventBean[] newData, EventBean[] oldData)
ViewIf 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.