Release Notes / Version 13.2512.0
Table Of ContentsDeprecation of Adaptive Personalization
The integration of Adaptive Personalization is deprecated in favor of the new Native Personalization.
Follow Section, “Deprecation of Adaptive Personalization” for upgrade information.
(CMS-29078)
Removed unused code from UriComponentsHelper
Unused code has been removed from the
com.coremedia.objectserver.web.links.UriComponentsHelper.
This results in removed and renamed public methods.
Follow Section, “Removed unused code from UriComponentsHelper” for upgrade information.
(CMS-28780)
Adaptive Personalization (p13n) Extensions Disabled By Default
The Adaptive Personalization extensions have been disabled by default in the Blueprint.
Follow Section, “Adaptive Personalization (p13n) Extensions Disabled By Default” for upgrade information.
(CMS-28763)
gRPC as an Alternative to CORBA Communication
For internal communication between CoreMedia CMCC components, gRPC has been added as an alternative to CORBA. Communication via CORBA is still available and the default. As long as you plan to stick with CORBA, no changes to your code or operations procedures are required. Should you want to switch to gRPC as your communications protocol between CMCC components, the following sections will provide information and pointer for additional details to do so.
In the course of adding gRPC as a communications protocol, however, breaking changes were introduced:
The old workflow client API and its implementations have been removed. They were actually unused after removing the Site Manager. This API was deprecated with 2406.2.2 and 2506.0.2. This affects the classes in the following packages:
com.coremedia.workflowcom.coremedia.workflow.common.utilcom.coremedia.workflow.worklist
Public workflow server API has been moved. The Java packages of the affected classes didn’t change, but they are now contained in Java artifact
com.coremedia.cms:cap-workflow-serverinstead ofcom.coremedia.cms:cap-workflow. Consequently, they cannot be used in extensions other than for the workflow server anymore. For clients, please use the Unified API. Documentation for the moved classes used to be at CoreMedia Shared Common API [ |https://documentation.coremedia.com/cmcc-12/artifacts/2506.0.0/javadoc/common/com/coremedia/workflow/package-summary.html] and can now be found at CoreMedia Workflow Server API .
Follow Section, “gRPC as an Alternative to CORBA Communication” for upgrade information.
(CMS-28689)
CORS Configuration Updated
In case you have existing CORS configuration, change your config from
caas.cors. to
cors. according to the deployment
manual.
(CMS-28541)
Removed redundant dependency management from blueprint parent POMs
Imports for Spring dependencies have been removed from the
dependencyManagement sections from the
blueprint-parent POMs.
Follow Section, “Removed redundant dependency management from blueprint parent POMs” for upgrade information.
(CMS-28515)
Removed util class InputInput
The class com.coremedia.util.InputInput has been
removed. It’s only usage in the content server’s
hox.corem.server.media.jdbc.BlobStore, dynamically
determining the length of uploaded blobs, has been replaced with util
classes from
Apache
Commons IO .
(CMS-28497)
Do not start MongoDB and Elastic Worker by default
Due to several changes (Removal of Google Analytics connectors,
Disabling of Elastic Social by default, Changing Collaborative
Component persistence to SQL) the Blueprint Docker deployment has been
adjusted to not start MongoDB and Elastic Worker by default. To start
them, please use the compose files elastic.yml and
development-elastic.yml.
(CMS-28438)
Removed deprecated BaseFileSystemConfiguration from ContentHub API
The class BaseFileSystemConfiguration has been
removed as it is not needed anymore and might cause confusion.
Follow Section, “Removed deprecated BaseFileSystemConfiguration from ContentHub API” for upgrade information.
(CMS-28214)
Content hub adapters are no longer delivered as bundled plugins
In previous versions the content hub adapters for youtube and rss were bundled in the studio-server and studio-client. The plugins are no longer bundled and have to be added like other plugins in each project.
(CMS-28213)
CatalogPicture#getUrl() removed from template api
CatalogPicture#getUrl() must not be used from templates, therefore it has been removed from the template api.
(CMS-28177)
Removed Deprecated API: Predicates
The deprecated class
com.coremedia.common.util.Predicates has been
removed from the Java API.
(CMS-28146)
Removal of Analytics Connectors
The integration of Analytics Connectors based on Elastic Core has been
removed, i.e. extension es-alx and parts of
extension alx, including the analytics doctypes.
Functionality for website tracking is still available and the
corresponding documentation has moved to the CoreMedia Blueprint
manual.
Follow Section, “Removal of Analytics Connectors” for upgrade information.
(CMS-28074)
Elastic Social (es) Extensions Disabled By Default
The Elastic Social extensions have been disabled by default in the Blueprint.
Follow Section, “Elastic Social (es) Extensions Disabled By Default” for upgrade information.
(CMS-28072)
Support for MySQL 8.0 and PostgreSQL 13 has been removed
Please update to supported versions MySQL 8.4 / PostgreSQL 16.
(CMS-27936)
The workflowconverter initscript has been removed from the workflow-server image
The recommended way to run the workflowconverter is either by running
it in-place at application startup activated by the flag
workflow.server.enable-workflow-converter or by
running the converter tool as an initcontainer or manually, when the
workflow-server is stopped.
(CMS-27806)
Confd has been removed from the management-tools image
Confd had been used as a convenience layer to reconfigure the tools based on environment variable based profiles. With confd it was possible configure arbitrary files using a templating mechanism.
Follow Section, “Confd has been removed from the management-tools image” for upgrade information.
(CMS-27753)
Middle Tier: Removal of Deprecated API
Follow Section, “Middle Tier: Removal of Deprecated API” for upgrade information.
(CMS-27564)
Common Tier: Removal of Deprecated API
The following deprecated classes and methods have been removed:
com.coremedia.blueprint.base.navigation.context.ContextStrategy#selectContextcom.coremedia.cache.CacheCapacityConfigurercom.coremedia.cap.common.Blob#getSizecom.coremedia.cms.common.plugins.beans_for_plugins.CommonBeansForPluginsConfigurationcom.coremedia.common.logging.MarkerFactory#getMarkercom.coremedia.dispatch.InterfaceOnlyPredicatecom.coremedia.livecontext.ecommerce.asset.AssetService#getDefaultPicturecom.coremedia.livecontext.ecommerce.common.CommerceIdProvider#formatProductTechIdcom.coremedia.livecontext.ecommerce.common.CommerceIdProvider#formatProductVariantTechIdcom.coremedia.livecontext.ecommerce.common.CommerceIdProvider#formatCategoryTechIdcom.coremedia.livecontext.ecommerce.user.UserContext#getCookieHeadercom.coremedia.livecontext.ecommerce.user.UserContext.Builder#withCookieHeadercom.coremedia.xml.UnsafeJdkJaxpFactorycom.coremedia.xml.XmlUtil5#escape
Follow Section, “Common Tier: Removal of Deprecated API” for upgrade information.
(CMS-27557)
Third-Party Update: Apache Solr 9.10.0
Apache Solr has been updated to version 9.10.0 and the coremedia/solr-base Docker image with tag 2.6-cm-9.10.0 has been released. As part of this change, the following transitive dependencies of Apache SolrJ have been updated:
Apache Zookeeper 3.9.4
Eclipse Jetty 10.0.26
Follow Section, “Third-Party Update: Apache Solr 9.10.0” for upgrade information.
(CMS-27540)
Discontinue base image flavors
The java-application-base image no longer provides jdk based image flavors. The jre for corretto and temurin is an adjusted custom jre based on the default jre module set with the addition of jshell.
(CMS-27499)
Switched to spring-grpc
Switched from
grpc-spring
to
spring-grpc.
This change causes that properties below
grpc.server and grpc.client are
no longer relevant. Instead the properties below
spring.grpc.server}}and {{spring.grpc.client}}must be used respectively. Along with this change, the commerce hub client setting {{com.coremedia.blueprint.base.livecontext.client.settings.CommerceSettings#getEndpoint}}was removed. Use `{{com.coremedia.blueprint.base.livecontext.client.settings.CommerceSettings#getEndpointName}}instead and configure an ops-friendly symbolic name, which is then configured as a named gRPC channel below {{spring.grpc.client.channels.
More specifically, this means that your
commerce}}struct’s {{endpoint}}value is no longer picked up to establish a commerce connection. Introduce a String property named {{endpointName}}in your {{commerce}}struct and give it the value of a gRPC channel, such as {{hybris}}or {{sfcc.
(CMS-27495)
Java 21 Support
Starting with CMCC v13.2512.0.0 the required JDK to build the workspace and run the applications is Java 21 LTS Release.
Follow Section, “Java 21 Support” for upgrade information.
(CMS-27319)
Removal of deprecated Commerce Hub Data properties
The following deprecated properties have been removed. Use their replacements in parentheses '(…)' instead.
commerce.hub.data.deadline(grpc.client.default-timeout)commerce.hub.data.services-without-timeout(grpc.client.service-timeouts)
The property commerce.hub.data.endpoints has been
removed without direct property replacement. Instead, use the
endpointName of the commerce
settings struct (respectively
com.coremedia.blueprint.base.livecontext.client.settings.CommerceSettings#getEndpointName)
to configure the Commerce Hub connection.
(CMS-27298)
Removed Deprecated API for Custom Proactive Engine Application
Custom Proactive Engine / Persistent Cache applications are not
supported anymore. Proactive Engine and Persistent Cache are internal
technical components of the CAE Feeder that
cannot be used in custom applications outside of the CAE
Feeder anymore. The Maven artifact
com.coremedia.cms:proactiveengine-component and
deprecated public Java API have been removed.
Follow Section, “Removed Deprecated API for Custom Proactive Engine Application” for upgrade information.
(CMS-27251)
Studio-Client Docker build improvements
The Studio-Client Docker build has been simplified to provide a better convenience when building the image. All three Dockerfiles (Dockerfile, Dockerfile.tooling and Dockerfile.tasks) have been merged into a single Dockerfile which is then preconfigured using a Docker Bakefile.
Follow Section, “Studio-Client Docker build improvements” for upgrade information.
(CMS-26030)
Support for Microsoft SQL Server (MSSQL) has been removed
As announced, the support for the database Microsoft SQL Server (MSSQL) has been removed from the product.
(CMS-25905)
Change Storage Layer of Collaborative Components to SQL
The Collaborative Components (My Edited Content, Projects, Workflow Archive, Notifications) now store their data in an SQL database instead of MongoDB. MongoDB and the In-Memory replacement are not supported any longer for these features, but can still be enabled for instance to prepare a data migration. For instructions on data migration and further details please see the section Collaborative Components in the Operation Basics Manual.
(CMS-25582)


