Difference between revisions of "EclipseLink/UserGuide/JPA/Basic JPA Development/Caching/Expiration"
|Line 4:||Line 4:|
Revision as of 15:11, 4 May 2011
|Mailing List • Forums • IRC • mattermost|
|Open • Help Wanted • Bug Day|
By default, objects remain in the session cache until they are explicitly deleted or garbage collected when using a weak identity map.
Alternatively, you can configure any object with a CacheInvalidationPolicy that lets you specify, either automatically or manually, under what circumstances a cached object is invalid: when any query attempts to read an invalid object, EclipseLink will go to the data source for the most up-to-date version of that object, and update the cache with this information.
You can use any of the following CacheInvalidationPolicy instances:
- DailyCacheInvalidationPolicy: the object is automatically flagged as invalid at a specified time of day.
- NoExpiryCacheInvalidationPolicy: the object can only be flagged as invalid by explicitly calling org.eclipse.persistence.sessions.IdentityMapAccessor method invalidateObject.
- TimeToLiveCacheInvalidationPolicy: the object is automatically flagged as invalid after a specified time period has elapsed since the object was read.
You can configure a cache invalidation policy in the following ways:
- At the project level that applies to all objects
- At the descriptor level to override the project level configuration on a per-object basis
- At the query level that applies to the results returned by the query
If you configure a query to cache results in its own internal cache, the cache invalidation policy you configure at the query level applies to the query's internal cache in the same way it would apply to the session cache.
If you are using a coordinated cache (see Cache Coordination), you can customize how EclipseLink communicates the fact that an object has been declared invalid.