com.ibm.etools.systems.subsystems.impl
Class AbstractCacheManager
java.lang.Object
com.ibm.etools.systems.subsystems.impl.AbstractCacheManager
- All Implemented Interfaces:
- ICacheManager
- public abstract class AbstractCacheManager
- extends Object
- implements ICacheManager
Abstract implementation of ICacheManager. Can be used by cache manager to provide some
basic caching helper methods.
Method Summary |
boolean |
isRestoreFromMemento()
Check if the Remote System Explorer is restoring a remote object
from a memento. |
void |
setRestoreFromMemento(boolean restore)
This flag is set if the Remote System Explorer is restoring a remote object
from a memento. |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
Copyright
public static final String Copyright
- See Also:
- Constant Field Values
AbstractCacheManager
public AbstractCacheManager()
setRestoreFromMemento
public void setRestoreFromMemento(boolean restore)
- Description copied from interface:
ICacheManager
- This flag is set if the Remote System Explorer is restoring a remote object
from a memento. This gives the subsystem the option to restore from the cache
instead of connecting to the remote system.
- Specified by:
setRestoreFromMemento
in interface ICacheManager
- Parameters:
restore
- true if the RSE is currently restoring a remote object associated
with this cache manager from a memento, otherwise false.
isRestoreFromMemento
public boolean isRestoreFromMemento()
- Description copied from interface:
ICacheManager
- Check if the Remote System Explorer is restoring a remote object
from a memento.
- Specified by:
isRestoreFromMemento
in interface ICacheManager
- Returns:
- true if the RSE is currently restoring a remote object associated
with this cache manager from a memento, otherwise false.
Copyright © 2005 IBM Corp. All Rights Reserved.
Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.