org.gvsig.tools.observer

Interface ComplexObservable

All Known Subinterfaces:

ComplexWeakReferencingObservable, CoverageStore, CoverageStoreProviderServices, DataStore, DataStoreInitializer2, FeatureReferenceSelection, FeatureSelection, FeatureStore, FeatureStore, RasterDataStore

All Known Implementing Classes:

AbstractRasterDataStore, BaseWeakReferencingObservable, DefaultCoverageStore, DefaultFeatureReferenceSelection, DefaultFeatureSelection, DefaultFeatureStore, DefaultFolderSet, DefaultRasterStore, DefaultRemoteRasterStore, DelegateWeakReferencingObservable, DynObjectSetFeatureSetFacade, DynObjectSetRasterInfo, DynObjectSetWCSInfo, DynObjectSetWMSInfo, DynObjectSetWMTSInfo, JToggleButtonHeaderCellRenderer, JToggleButtonHeaderCellRenderer, ProjectManager

public interface ComplexObservable

Method Summary

Modifier and Type	Method and Description
void	beginComplexNotification() Sets the Observable in complex notification mode.
void	disableNotifications() Disable the notification of events to registered Observers.
void	enableNotifications() Enable (default) the notification of events to registered Observers.
void	endComplexNotification() Ends the complex notification mode.

Method Detail

disableNotifications

void disableNotifications()

Disable the notification of events to registered Observers.

enableNotifications

void enableNotifications()

Enable (default) the notification of events to registered Observers.

beginComplexNotification

void beginComplexNotification()

Sets the Observable in complex notification mode. All notifications must be stored, until the mode ends, and then notify all Observers with all the notifications.

endComplexNotification

void endComplexNotification()

Ends the complex notification mode. All notifications stored while in complex notification mode, will be notified to the registered Observers.

If a observer is a ComplexObserver, it will be notified with a single DefaultComplexNotification instead of each of the notifications.

Some important notes to take into account when calling this method.

• Observers must not rely in the order used to perform the notifications. The notifications order is maintained, but the notification to all the observers might be performed for each notification to all observers, or for each observer all notifications.
• The notification process works as an atomic action, so if while an Observer is processing a notification another Observer is registered to the source Observable, it won't get any of the notifications currently being notified, but future ones.