Minor API Change in WorkflowObject

The return type of com.coremedia.cap.workflow.WorkflowObject#getWarnings has been weakened from List<WorkflowException> to List<CapException>. Due to a CMS internal generics inconsistency the result list of getWarnings may contain CapException objects even in older CMS versions. This fix does not change the behaviour, but only clarifies the type. Custom code may have to be adjusted accordingly.

(CMS-29380)

Removed Built-in Search and Replace Workflows

The built-in workflow definitions global-search-replace.xml and markup-search-replace.xml have been removed. These definitions were used with the Site Manager, which has already been removed in CMCC 12.

(CMS-29293)

Configuration for Command Line Tool "publishall" Changed

Command Line Tool publishall was previously configurable with non-option arguments: cm publishall [ -a [ -cq <query> ] ] [ -t <threads> ] <cmsiorurl> <cmsuser> <cmspwd> <masteriorurl> <masteruser> <masterpwd>. With the introduction of gRPC as the communication protocol and the need for additional parameters, the configuration was adjusted and unified. Instead of non-option arguments, now all configuration has to be given as options.

Follow Section, “Configuration for Command Line Tool "publishall" Changed” for upgrade information.

(CMS-28803)

Feeder caches results of Tika text extraction

Content Feeder and CAE Feeder now cache the results of Apache Tika text and metadata extraction for indexed blob values. This improves feeding performance, if content is re-indexed with unchanged blob value, or if the same blob value is used in multiple content items. The Blueprint configures a default cache capacity of estimated 10 MB heap memory using configuration property cache.capacities.feeder.tika.heap in application.properties. Because of that, Feeders require slightly more heap memory. Caching can be disabled by setting the cache capacity to 0.

(CMS-28599)

Support for personalization variants

In order to support personalization variants, a new meta-property variant was added to Content items. It is immutable once set during content creation. It is accessible through isVariant() and its inverse isBaseline(). For a baseline content item, multiple variants may be created. Variants are created with the same content type as their baseline. They are used for delivering A/B tests or specialized content for user segments.

Follow Section, “Support for personalization variants” for upgrade information.

(CMS-28490)

CAE Feeder Renamed Cache Class for Internal Caching

The CAE Feeder uses in-memory cache keys for caching fragment values returned by Java method com.coremedia.cap.persistentcache.PersistentCache#getCached. The cache class of these internally used cache keys has changed from the generic cache class java.lang.Object to the new cache class com.coremedia.cap.persistentcache. The default cache capacity of 10000 entries is the same as the Blueprint’s default for the previously used cache class. For details, see also section “Getting the Fragment Key Value from the Persistent Cache” in the Search Manual.

(CMS-28413)

Removed Deprecated Method in AssetDocumentBlobFeedablePopulator

Removed deprecated method setMaxBytes of Blueprint class com.coremedia.blueprint.feeder.cae.assets.AssetDocumentBlobFeedablePopulator. Use configuration property feeder.blob.max-size instead to limit feeding of blobs by their size.

(CMS-28375)

Removed Deprecated Classes ValidFromPropertyConverter / ValidToPropertyConverter

Removed deprecated Blueprint Java classes ValidFromPropertyConverter and ValidToPropertyConverter in package com.coremedia.blueprint.caefeeder.

(CMS-28374)

Removal: Deprecated Java API Package com.coremedia.cap.server.search

The following deprecated interfaces and classes of package com.coremedia.cap.server.search have been removed from the Java API:

(CMS-27992)

Removal of XML Importer

The deprecated XML Importer has been removed. As a replacement, a custom Unified API client, the Ingest Service for CoreMedia Content Cloud Service or the serverimport tool should be used.

Follow Section, “Removal of XML Importer” for upgrade information.

(CMS-27871)

Hardened Server- and XLIFF-Export for Invalid XML Control Characters

The output of cm serverexport as well as the resulting XLIFF from XLIFF-Export have been hardened to not output invalid XML control characters. If these characters made it into the XML/XLIFF-files parsers fail reading them afterward.

Invalid control characters range from 0x0000 (NUL) to 0x001F (Information Separator One (US - Unit Separator)) except for 0x0009 (Horizontal Tab), 0x000A (Line Feed) and 0x000D (Carriage Return). On export, these control characters are now removed, so that they don’t block subsequent import.

One exception to this rule: For attributes name and folder of a given exported content item, URL-encoding is applied to them now, just as it is already done for internal representation (in link lists as well as in links in Rich Text and Structs).

Specification Level 1: With this change we introduce a “specification level” explicitly noted in files created by serverexport such as:

<CMChannel
  specification="1"
  folder="/Sites/Chef%20Corp%2E/United%20States/English/Navigation"
  name="Chef%20Corp%2E%20USA%20Home%20Page"
  xmlns:cmexport="http://www.coremedia.com/2012/cmexport">
  <!-- ... -->
</CMChannel>

Follow Section, “Hardened Server- and XLIFF-Export for Invalid XML Control Characters” for upgrade information.

(CMS-27456)

CAE Feeder Spring Configuration Changes and Deprecations

The Blueprint CAE Feeder Spring configuration was changed to use Spring Java configuration classes instead of legacy Spring XML files. This makes it possible to use Java code to configure which content bean data should be indexed. Instead of configuring content bean classes and properties as literal string values, the configuration can now use more reliable Java code to refer to methods directly. To this end, new addElement methods have been added in class com.coremedia.cap.feeder.bean.BeanFeedableMapping while API for old-style Spring XML configuration has been deprecated.

Follow Section, “CAE Feeder Spring Configuration Changes and Deprecations” for upgrade information.

(CMS-27398)

Removed cm groovysh

We removed the command line tool cm groovysh in favor of the more mature solution for ad-hoc Unified API scripting and more using cm jshell that we ship since CMCC v10.2004.1.

Follow Section, “Removed cm groovysh” for upgrade information.

(CMS-25885)

Deprecated Workflow JAR Upload Disabled by Default

The deprecated feature to upload JAR files with classes, and to use classes from previously uploaded JAR files in workflow process definitions has been disabled by default, and may be removed in a future release. Required classes should be added to the Workflow Server classpath instead.

Follow Section, “Deprecated Workflow JAR Upload Disabled by Default” for upgrade information.

(CMS-23931)

Removed Obsolete Property sql.store.login-user-name

The property sql.store.login-user-name has become obsolete and has been removed. Just use sql.store.user instead.

Follow Section, “Removed Obsolete Property sql.store.login-user-name” for upgrade information.

(CMS-23177)

Content Server Database Change

When the Content Server starts the first time after upgrading, it will automatically remove the no longer needed foreign key constraint fk_WfV_group on column groupValue_0 of table WfVariables for existing Oracle, MariaDB and MySQL databases.

Follow Section, “Content Server Database Change” for upgrade information.

(CMS-18857)