Home/ Questions/Q 3454756
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T09:31:51+00:00

Not only this but also org.hibernate.cache.Cache.CacheProvider is also deprecated. If these are then how

  • 0

Not only this but also org.hibernate.cache.Cache.CacheProvider is also deprecated.

If these are then how are we supposed to create our own custom Caching Solutions ?
Alternate method ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The JavaDoc explains it:

    The legacy (and now deprecated) approach to caching is defined by the CacheProvider and Cache interfaces as well as the CacheConcurrencyStrategy interface along with the various implementations of all these interfaces. In that scheme, a CacheProvider defined how to configure and perform lifecycle operations in regards to a particular underlying caching library; it also defined how to build Cache instances which in turn defined how to access the "regions" of the underlying cache instance. For entity and collection data cache regions, CacheConcurrencyStrategy wrapped access to those cache regions to apply transactional/concurrent access semantics.

    The improved approach is based on RegionFactory, the various Region specializations and the two access strategies contracts (EntityRegionAccessStrategy and CollectionRegionAccessStrategy).

    To sum it up, there is a new improved API you should use.

    • 0