| Behavioral interface that is implemented by
DataProvider classes
that offer commit/revert support. In such environments, methods that modify
the data element values (such as setValue()) must cause the new
values to be cached, and the underlying data elements are not actually
updated until commitChanges() is called. An application may
also call revertChanges() to throw away any cached updates. In
spite of this caching, however, valueChanged() events must still
be sent to registered
DataListener s -- an instance of
TransactionalDataListener will also be notified when the
actual commitChanges() or revertChanges() occurs.
During the time between when a modification method (such as
setValue() is called, and a later call to
commitChanges(), any calls to getType() or
getValue() will reflect the modified value from the cache, not
the original value from the underlying data structure.
author:
Craig McClanahan
author:
Joe Nuxoll |