[
https://issues.apache.org/jira/browse/JDO-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Jefferson updated JDO-599:
-------------------------------
Attachment: api2_schema.patch
api2-legacy_schema.patch
api2_annotations.patch
Patches for
1. updating jdo.xsd for api2 and api2-legacy to add "cacheable" attribute to
<class>, <interface>, <field>, <property>
2. adding @Cacheable annotation, and adding "cacheable" property to
@PersistenceCapable and @Persistent
> Level 2 Caching ability to restrict what classes/fields are cahed
> -----------------------------------------------------------------
>
> Key: JDO-599
> URL: https://issues.apache.org/jira/browse/JDO-599
> Project: JDO
> Issue Type: New Feature
> Components: api2, api2-legacy, specification
> Reporter: Andy Jefferson
> Fix For: JDO 2 maintenance release 2
>
> Attachments: api2-legacy_schema.patch, api2_annotations.patch,
> api2_schema.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
