Commerce Hub Invalidation Events Added

CMS applications with commerce client integration can now receive cache invalidation events. With this, commerce items are invalidated in the cache of the client applications if the commerce adapter sends an invalidation event, which may be triggered automatically due to change detection (if applicable) or manually using the commerce adapter's invalidate actuator endpoint. This feature only works when the client applications are connected to supporting (new) commerce adapter versions. Please see the release notes of the commerce adapters for further information.

(CMS-19482)

Deprecated the commerce connection's 'forVendor' methods

Deprecated com.coremedia.livecontext.ecommerce.common.CommerceConnection#getServiceForVendor and com.coremedia.livecontext.ecommerce.common.CommerceConnection#getQualifiedServiceForVendor . Only use the com.coremedia.livecontext.ecommerce.common.ForVendor annotation to customize the com.coremedia.blueprint.base.livecontext.client.common.GenericCommerceConnection . Resort to com.coremedia.blueprint.base.livecontext.ecommerce.common.CommerceServicesForVendor if legacy commerce connections are used.

(CMS-19123)