org.exolab.castor.jdo
public class CacheManager extends Object
Version: $Revision: 1.3 $ $Date: 2005/06/20 12:01:00 $
Constructor Summary | |
---|---|
CacheManager(Database db, TransactionContext transactionContext, LockEngine lockEngine)
Creates an instance of this class. |
Method Summary | |
---|---|
void | dumpCache()
Dump all cached objects to log. |
void | dumpCache(Class cls)
Dump cached objects of specific type to log. |
void | expireCache()
Expires all objects from cache.
|
void | expireCache(Class type, Object identity)
Expires a type with a specific identity from cache.
|
void | expireCache(Class type, Object[] identity)
Expires a type with specific identities from cache.
|
void | expireCache(Class[] type)
Expires all instances of specified types from cache.
|
boolean | isCached(Class cls, Object identity)
Indicates whether am instance of cls is currently cached |
Parameters: db Database instance. transactionContext Active transaction context. lockEngine Lock engine
Objects expired from the cache will be read from persistent storage, as opposed to being read from the performance cache, during subsequent load/query operations.
When objects are expired from the cache individually, by identity, objects contained within a "master" object, for example objects maintained in a one-to-many relationship, will automatically be expired from the cache, without the need to explicitly identify them. This does not apply when expiring objects by type. Each type, both container and contained objects need to be specified.
Objects expired from the cache will be read from persistent storage, as opposed to being read from the performance cache, during subsequent load/query operations.
When objects are expired from the cache individually, by identity, objects contained within a "master" object, for example objects maintained in a one-to-many relationship, will automatically be expired from the cache, without the need to explicitly identify them. This does not apply when expiring objects by type. Each type, both container and contained objects need to be specified.
Parameters: type The type to expire. identity Identity of the object to expire.
Objects expired from the cache will be read from persistent storage, as opposed to being read from the performance cache, during subsequent load/query operations.
When objects are expired from the cache individually, by identity, objects contained within a "master" object, for example objects maintained in a one-to-many relationship, will automatically be expired from the cache, without the need to explicitly identify them. This does not apply when expiring objects by type. Each type, both container and contained objects need to be specified.
Parameters: type The type to expire. identity An array of object identifiers to expire.
Objects expired from the cache will be read from persistent storage, as opposed to being read from the performance cache, during subsequent load/query operations.
When objects are expired from the cache individually, by identity, objects contained within a "master" object, for example objects maintained in a one-to-many relationship, will automatically be expired from the cache, without the need to explicitly identify them. This does not apply when expiring objects by type. Each type, both container and contained objects need to be specified.
Parameters: type An array of types to expire.
Parameters: cls The class type. identity The object identity.
Returns: True if the object is cached.
Throws: PersistenceException If a problem occured resolving the object's cache membership.