Skip Headers

# Configuring Cache Isolation at the Descriptor Level

Previous

Next

If you plan to use isolated sessions (see "Cache Isolation"), you must configure descriptors as isolated for any object that you want confined to an isolated session cache.

Configuring a descriptor to be isolated means that TopLink will not store the object in the shared session cache and the object will not be shared across client sessions. Each client will have their own object read directly from the database. Objects in an isolated client session cache can reference objects in their parent server session's shared session cache, but no objects in the shared session cache can reference objects in an isolated client session cache. Isolation is required when using Oracle Database Virtual Private Database (VPD) support or database user-based read security. Isolation can also be used if caching is not desired across client sessions.

Table: Descriptor Support for Identity Map summarizes which descriptors support cache isolation configuration.

Descriptor Support for Cache Isolation Map

Descriptor | Using TopLink Workbench | Using Java
--- | --- | ---
Relational DescriptorsFoot 1 |  |
Object-Relational Descriptors |  |
EIS DescriptorsFoot 2 |  |
XML Descriptors |  |

Footnote 1 Relational class descriptors only (see "Relational Class Descriptors").

Footnote 2 EIS root descriptors only (see "EIS Root Descriptors").

This configuration overrides the default cache isolation configuration defined at the project level (see "Configuring Cache Isolation at the Project Level").

Note: If a descriptor is a child in an inheritance hierarchy, TopLink makes the Caching tab read-only and displays the options from the root descriptor in the inheritance hierarchy.

Note: If you configure a descriptor as isolated, it cannot participate in a coordinated cache (see "Configuring Cache Coordination Change Propagation at the Descriptor Level").