Handler of content change events.
The presence of this marker interface on a
indicates that cluster external observation events must not be reported to that
A filter is used by the FilteringObserver to decide whether or not a content
change should be forwarded.
A FilteringAwareObserver is the stateless-variant of
an Observer which gets an explicit before as well as the
A ChangeCollectorProvider can be hooked into Oak thus enabling the collection
of ChangeSets of changed items of a commit, which downstream Observers can
then use at their convenience.
CommitHook can be used to block or delay commits for any length of time.
Default implementation of
Continuation-based content diff implementation that generates
callbacks by recursing down a content diff
in a way that guarantees that only a finite number of callbacks
will be made during a
method call, regardless
of how large or complex the content diff is.
Filtered event handler.
Part of the FilteringObserver: the FilteringDispatcher is used
to implement the skipping (filtering) of content changes
which the FilteringDispatcher flags as NOOP_CHANGE.
An observer that implements filtering of content changes
while at the same time supporting (wrapping) a BackgroundObserver
Base class for
Observer instances that group changes
by node instead of tracking them down to individual properties.