loading table of contents...

Release Notes / Version 11.2110

Table Of Contents

CoreMedia Commerce Hub

Removal: Special Commerce Hub API for Preview URLs

The special treatment of Studio preview urls has been removed from Commerce Hub API. Now preview urls are generated the same way as the other commerce related links via LinkTemplates and dynamic replacement values. Most of the changes took place within the commerce adapter workspaces. On the CMS side the PreviewUrlService has been deleted and there are changes in the CommerceStudioLinks.

Follow Section, “Removal: Special Commerce Hub API for Preview URLs” for upgrade information.


Updated Multi Catalog Configuration

The catalog alias configuration for the multi catalog feature has been updated. The former Studio content configuration setting "livecontext.catalogAliases" has been removed and needs to be updated, if you use multiple catalogs for one site. If you do not use the multi catalog feature there is no action required.

Follow Section, “Updated Multi Catalog Configuration” for upgrade information.


Removal: Deprecated Methods and Implementation

Removed deprecated methods getCapacity/getCacheTimesInSeconds of class com.coremedia.blueprint.base.livecontext.ecommerce.common.CommerceCache . Also removed its isEnabled method because the commerce cache can no longer be disabled.

Follow Section, “Removal: Deprecated Methods and Implementation” for upgrade information.


Removal: LC3 SearchService

Removed the interface because commerce hub does not support search suggestions. Search is supported via com.coremedia.livecontext.ecommerce.catalog.CatalogService#search .


Removal: Deprecated Developer Feature Candy Shop URLs

The deprecated developer feature "Candy Shop URLs" has been removed from the Blueprint. There is no replacement planned, developers will need to configure their local machine in the shop configuration to retrieve fragments from their localhost. Frontend development is easily possible through the Frontend Developer workflow and uploading of local Themes to the CMS.


CurrentStoreContext and UserStoreContext API change

Deprecated methods have been removed from com.coremedia.blueprint.base.livecontext.ecommerce.common.CurrentStoreContext and com.coremedia.blueprint.base.livecontext.ecommerce.common.CurrentUserContext .

Follow Section, “CurrentStoreContext and UserStoreContext API change” for upgrade information.


Removal: Obsolete Base Classes from LiveContext Test Modules

With the introduction of the Commerce Hub, the connections to commerce systems have been moved away from the central CMS services to the commerce adapters. After all legacy LiveContext extensions (those, that don't use the commerce adapters) have been removed, their base test classes are now obsolete and have also been removed.


Removal: Hoverfly Extension Classes from LiveContext Test Modules

With the introduction of the Commerce Hub, the connections to commerce systems have been moved away from the central CMS services to the commerce adapters. The tests that require commerce connections (whose requests and responses can be recorded and replayed with Hoverfly) have been moved, too, making the Hoverfly extension classes in LiveContext test modules obsolete, hence they have now been removed.


Removal: Deprecated Legacy Search API from LiveContext Extensions

CMCC11 doesn't support old adapter versions with legacy search API anymore. Legacy commerce client API and implementations have been removed. This includes:

Follow Section, “Removal: Deprecated Legacy Search API from LiveContext Extensions” for upgrade information.


Removal: Deprecations from LiveContext API

The old LiveContext API is used to access the Commerce Hub / generic commerce client from Studio and other clients. Some deprecations have now been deleted that are not needed anymore or that are not supported by the Commerce Hub. They are in detail: the AvailabilityService (not supported by the CommerceHub, should be requested directly from the commerce system), UserServer and UserSessionService (not needed anymore, the whole part of session sync between the CMS and the commerce system is gone, only the login/logout can be done via the commerce adapter), the AssetUrlProvider (is also not needed anymore).


Removal: Deprecated lc-extension Related LinkSchemes

Obsolete deprecated linkschemes used for commerce integration via lc-extension have been deleted.


Removal: com.coremedia.blueprint.base.livecontext.service Package

The deprecated com.coremedia.blueprint.base.livecontext.service package has been removed without replacement as it was part of the legacy Blueprint commerce integration. The Commerce Hub integration does not yet offer corresponding classes dealing with connections to Storefront services.

Follow Section, “Removal: com.coremedia.blueprint.base.livecontext.service Package” for upgrade information.


Removal: Deprecated Livecontext Classes and Methods

The classes AbstractCommerceBean  and SpringCommerceBeanFactory from package com.coremedia.blueprint.base.livecontext.ecommerce.common were removed. Use com.coremedia.blueprint.base.livecontext.client.beans.ClientCommerceBeanFactoryMethodRegistry instead.

Follow Section, “Removal: Deprecated Livecontext Classes and Methods” for upgrade information.


Removal: Deprecated Commerce Cache Invalidation Implementation

The deprecated source code for the Commerce Cache Invalidation of the LiveContext 3 extensions has been removed. Customizations based on that implementation have to be updated to work with the commerce cache invalidation implementation of the commerce hub (in commerce adapters and in the commerce hub client implementation).


Removal: The ForVendor-Methods from the CommerceConnection

Removed methods com.coremedia.livecontext.ecommerce.common.CommerceConnection#getServiceForVendor and com.coremedia.livecontext.ecommerce.common.CommerceConnection#getQualifiedServiceForVendor . Use class com.coremedia.blueprint.base.livecontext.ecommerce.common.CommerceServicesForVendor instead.


Simplified Registration of Custom Commerce Bean Types

The class com.coremedia.livecontext.ecommerce.common.CommerceBeanTypeRegistry was removed and com.coremedia.livecontext.ecommerce.common.CommerceBeanType was converted from an interface to an implementation class. Instead of registering enum classes defining custom commerce bean types you may now define custom commerce bean types on demand by calling com.coremedia.livecontext.ecommerce.common.CommerceBeanType#of(String) . This solves the issue of class loading order which occasionally lead to missing custom commerce bean types at runtime.

Follow Section, “Simplified Registration of Custom Commerce Bean Types” for upgrade information.


Removal: CommerceConnection#getClone Method

Removed com.coremedia.livecontext.ecommerce.common.CommerceConnection#getClone . Commerce Connection instances must not be modified after creation.


Search Results

Table Of Contents