Caching Objects

Database sessions include an identity map that maintains object identity, and acts as a cache. When the session reads objects from the database, it instantiates them and stores them in the identity map. When the application subsequently queries for the same object, OracleAS TopLink returns the object in the cache, rather than read the object from the database again.

You can force OracleAS TopLink to flush all objects from the cache. To do so, first ensure that none of the objects are in use within the database session. Then call the initializeIdentityMaps() method.

To improve performance, you can customize the identity map. For more information about using the identity map and caching, see the Oracle Application Server TopLink Mapping Workbench User's Guide.