db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Closed: (JDO-599) Level 2 Caching ability to restrict what classes/fields are cahed
Date Thu, 31 Jul 2008 20:02:32 GMT

     [ https://issues.apache.org/jira/browse/JDO-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Craig Russell closed JDO-599.

    Resolution: Fixed

The draft specification dated 30-July-2008 has been updated.

> 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
>            Assignee: Craig Russell
>             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
> 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.

View raw message