Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 356932 - [EclipseLink] support tenants-share-cache persistence unit property
Summary: [EclipseLink] support tenants-share-cache persistence unit property
Status: NEW
Alias: None
Product: Dali JPA Tools
Classification: WebTools
Component: JPA (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: Neil Hauge CLA
QA Contact:
URL:
Whiteboard: EclipseLink
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-07 09:33 EDT by Karen Butzke CLA
Modified: 2011-10-21 14:32 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karen Butzke CLA 2011-09-07 09:33:58 EDT
Add support for the persistence.xml property "eclipselink.multitenant.tenants-share-cache" The default is false. If it is set to true then all multitenant entities will have a PROTECTED cache (CacheIsolationType.PROTECTED). We need to make this the default for multitenant entities.

We probably need a validation error/warning if the cache isolation is set to something other than PROTECTED for a multitenant entity. That setting will just be ignored.
Comment 1 Karen Butzke CLA 2011-09-21 09:34:37 EDT
The default has been changed to ISOLATED, see bug 357476
Comment 2 Karen Butzke CLA 2011-10-06 10:49:15 EDT
     * Property <code>"eclipselink.multitenant.tenants-share-cache</code> 
     * specifies that multitenant entities will share the L2 cache. By default 
     * this property is false meaning multitenant entities will have an ISOLATED 
     * setting. When setting it to true a PROTECTED cache setting will be used.
     * 
     * WARNING: Queries that use the cache may return data from other tenants 
     * when using the PROTECTED setting.

We will not be adding a UI widget for this setting, it is an advanced and obscure setting and has potential security issues with setting it to true.
Comment 3 Karen Butzke CLA 2011-10-21 14:32:49 EDT
We will not need this support since we are not supporting bug 360594