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
(New page: = Cache APIs = JPA 2.0 Root | [http://bugs.eclipse.org/248780 Enhancement Request] ==Issue Summary== In JPA 2.0 the specification has added a Cache ...) |
(→Issue Summary) |
||
| Line 3: | Line 3: | ||
[http://bugs.eclipse.org/248780 Enhancement Request] | [http://bugs.eclipse.org/248780 Enhancement Request] | ||
==Issue Summary== | ==Issue Summary== | ||
| − | In JPA 2.0 the specification has added a Cache API obtainable from a | + | 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. | See JPA 2.0 ED section 5.10 for details. | ||
Revision as of 14:36, 29 September 2008
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