Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseLink/Development/JPA 2.0/cache api"
< EclipseLink | Development | JPA 2.0
(→Issue Summary) |
|||
| Line 16: | Line 16: | ||
# Implement API | # Implement API | ||
#: approx 2 days | #: approx 2 days | ||
| + | |||
| + | ==Implementation Details== | ||
| + | |||
| + | The Cache API consists of following 4 methods | ||
| + | |||
| + | #contains(Class cls, Object primaryKey) --- | ||
| + | #evict(Class cls, Object primaryKey) --- | ||
| + | #evict(Class cls) --- | ||
| + | #evictAll() --- | ||
Revision as of 16:09, 17 March 2009
Contents
Cache APIs
JPA 2.0 Root | Enhancement Request
Issue Summary
In JPA 2.0 the specification has added a Cache API obtainable from a EntityManagerFactory. This simple API provides developers with rudimentary access and control of a second level cache. User's can interrogate the cache through a 'contains' API and cause cached data to be evicted from the cache through 'evict' API.
See JPA 2.0 ED section 5.10 for details.
General Solution
Should be simple to equate evict to invalidate.
Work Required
- Develop tests
- approx 1 day
- Implement API
- approx 2 days
Implementation Details
The Cache API consists of following 4 methods
- contains(Class cls, Object primaryKey) ---
- evict(Class cls, Object primaryKey) ---
- evict(Class cls) ---
- evictAll() ---