[JDO-599] Level 2 Caching ability to restrict what classes/fields are cahed

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: JDO 2 maintenance release 2 (2.2)
• Component/s: api, api2-legacy, specification
• Assignee: Craig L Russell
• Reporter: Andy Jefferson
• Created: 12/Jul/08 06:43
• Updated: 31/Jul/08 20:00
• Resolved: 31/Jul/08 20:00

Description

Having more control over what goes into an L2 cache is desirable for some systems. Currently JDO(2) provides no control other than the pin/unpin/evict methods on the DataStoreCache. One way of providing more control would be to allow specification via metadata (XML/annotations) for classes/fields.

1. Add a "cacheable" attribute to class/field XML elements with default value of "true".
2. Add a "cacheable" property to @PersistenceCapable/@Persistent with default value of true.
3. Add a new annotation @Cacheable applicable to class/field/property

The user can then define particular classes to never be L2 cached, and also particular fields to never be L2 cached.