Dedicated Cache Class for Commerce Objects

Most of the commerce entities come along with their own cache class that can be used for capacity and cache duration configuration, which still should be used.

Others couldn't be configured explicitly and re-used the default configuration for "java.lang.Object". Now they can be configured via "ecommerce.object". The default configuration

cache.capacities.ecommerce.object=10000

should be sufficient for most cases.

No action is required.

List of cache keys that are affected:

com.coremedia.blueprint.base.ecommerce.catalog.CmsCatalogService.CommerceBeanCacheKey
com.coremedia.blueprint.base.ecommerce.catalog.RootCategoryContentCacheKey
com.coremedia.blueprint.base.livecontext.client.data.grpc.DataEndpointCacheKey
com.coremedia.blueprint.base.livecontext.ecommerce.common.CommerceSettingsCatalogConfigListCacheKey 
com.coremedia.blueprint.base.livecontext.ecommerce.common.SiteToCommerceConnectionCacheKey
com.coremedia.blueprint.base.livecontext.ecommerce.common.SiteToStoreContextCacheKey 
com.coremedia.blueprint.base.livecontext.ecommerce.common.StoreIdAndLocaleToSiteCacheKey 
com.coremedia.livecontext.context.LiveContextResolveContextStrategy.CommerceContextProviderCacheKey
com.coremedia.livecontext.view.ConfiguredContentTypesCacheKey

Upgrade Information

(CMS-28178)