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.

Propose:
Add a "cacheable" attribute to class/field XML elements with default value 
of "true".
Add a "cacheable" property to @PersistenceCapable/@Persistent with default 
value of true.

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


Comments ?
-- 
Andy  (DataNucleus - http://www.datanucleus.org)

Reply via email to