Merged Module bpbase-uapi-util into cap-unified-api-util

Since bpbase-uapi-util is actually not specific to bpbase features, there is no use keeping the UAPI utilities in two separate modules. Therefore, we merged the two modules, so that the features from bpbase-uapi-util are also available in the core layer now. If you use bpbase-uapi-util features in your project, you must change the package from com.coremedia.blueprint.base.util to com.coremedia.cap.util , and the Maven dependency from

Follow Section, “Merged Module bpbase-uapi-util into cap-unified-api-util” for upgrade information.

(CMS-15227)

Changed Names of Some Spring Boot Apps, Docker Images and Extension Points

With the integration of Spring Boot and Docker into the Blueprint workspace (they used to be separate workspaces in CM9/LC3) and the introduction of modular (sub-)workspaces, the Maven artifactIds and workspace names have been consolidated. Also, CAE Feeder and Content Server "flavors" (live/preview, management/master/replication) have been unified into one Spring Boot App / Docker image. Furthermore, studio-rest-service has been renamed to studio-server, and studio has been changed to studio-client where appropriate. The following artifactId changes have to be considered:

Follow Section, “Changed Names of Some Spring Boot Apps, Docker Images and Extension Points” for upgrade information.

(CMS-14794)

Merged Live and Preview CAE Feeder

CAE Feeder comes in two flavors: live and preview. Although the only difference is configuration, these used to be two separate components, Spring Boot applications, and Docker containers. Now, there is only one component, one Spring Boot application and one Docker container. Docker compose takes care of configuring two CAE Feeders, one for preview and one for live. For development, there are separate Spring and Maven profiles provided to start the CAE Feeder in the desired flavor.

(CMS-14785)

Merged Content Server flavors

The Content Server comes in three flavors: management, master-live and replication-live. Previously these used to be different components, Spring Boot applications and Docker images. Now, there is only one component, one Spring Boot application and one Docker container. The main difference between the flavors is the usage of the SearchService in the content-management-server, which now has to be enabled explicitly using the property cap.server.search.enable . Docker compose takes care of configuring three Content Servers, one as content-management-server, one as master-live-server and one as replication-live-server. For development, there are separate Spring and Maven profiles provided to start the Content-Server in the desired flavor.

(CMS-14782)

Removal: Class 'com.coremedia.workflow.common.util.MapRole'

Removed class 'com.coremedia.workflow.common.util.MapRole'.

Follow Section, “Removal: Class 'com.coremedia.workflow.common.util.MapRole'” for upgrade information.

(CMS-14147)

Defining custom translation workflow validators

The workflow validation was made public API. It is now possible to define custom translation workflow validators. This is documented within the Studio Manual in section "Customizing Workflow Validation".

(CMS-13761)

Solr 8 and SolrCloud

Apache Solr has been updated to version 8.1.1. Furthermore, Solr may also run as SolrCloud cluster for CMCC now.

Follow Section, “Solr 8 and SolrCloud” for upgrade information.

(CMS-13291)

Removal: Workflow Server's Internal Spring Context

The Workflow server no longer manages an internal Spring application context.

Follow Section, “Removal: Workflow Server's Internal Spring Context” for upgrade information.

(CMS-12425)

Changed Default Value of checkUniqueDbAccess

Changed default of cap.server.checkUniqueDbAccess to true; has been false for backwards compatibility only.

(CMS-12300)

ORB configuration

Since Java 11 does not contain a Corba ORB any longer, we switched to the Glassfish ORB. The Glassfish ORB originates from the same code base and is mostly compatible with the ORB included in Java 8. However, some things have changed (esp. property names), and since we could not avoid some breaking changes anyway, we seized the opportunity for some renovation of our Corba features:

Follow Section, “ORB configuration” for upgrade information.

(CMS-12067)

ConfigurationProperties for Servers

For the Content and Workflow Server ConfigurationProperties classes have been introduced that replace the different properties files used in the servers:

Follow Section, “ConfigurationProperties for Servers” for upgrade information.

(CMS-3030)

Changed Login Services and System Users

The login service and user for the connection to the Content Server have changed for Studio Server , CAE Feeder and User Changes App . In previous releases, all of these applications logged in as user "webserver" and with login service "webserver", which gave them rights to read and write all content, and to log in as different users without a password, for example to write content in the name of another user. This has been changed in order to give applications only the rights required for their operation. The Studio Server and the User Changes App now log in with the newly introduced login service "studio" and user "studio". The CAE Feeder now logs in with the existing login service "feeder" and user "feeder". The CAE and the Elastic Worker still use the login service "webserver" and user "webserver" but the rights of this account have been restricted.

Follow Section, “Changed Login Services and System Users” for upgrade information.

(CMS-378)

Changed Site Manager LookAndFeel for Windows

The WindowsLookAndFeel has vanished in Java 11 (was not public API, anyway). The CoreMediaLookAndFeel was derived from the WindowsLookAndFeel and brings no benefits for the LookAndFeel flavors available in Java 11. Therefore, we do not explicitly configure a LookAndFeel any longer in our default editor.xml , but simply stick to the Swing default. The CoreMediaLookAndFeel is still available and extends the NimbusLookAndFeel now. If you favor this over the Swing default LookAndFeel, you can keep on using it. Of course, you can still use your own custom LookAndFeel or the "system" LookAndFeel.

Follow Section, “Changed Site Manager LookAndFeel for Windows” for upgrade information.

(CMS-15198)

Made Serverimport More Deterministic

Serverexport is somewhat error prone due to the subtle behaviour of the cut feature. Hence, it easily happens that links in serverexport files are inconsistent wrt. their path and href values. The behaviour of serverimport in such cases depended on the order in which link source and target were imported, which in turn cannot be controlled, esp. if you import concurrently with the threads option. Sometimes the import succeeded, and sometimes it failed, and the serverimport deleted the apparently broken link.

Follow Section, “Made Serverimport More Deterministic” for upgrade information.

(CMS-14166)

Content Types must restrict master links to same type

The link type of link list property master is now restricted to link to the same type for content types AMTaxonomy , CMImageMap , CMLocTaxonomy , CMP13NSearch , CMTaxonomy , CMViewtype and ESDynamicList , instead of allowing super types. This should match values of existing content, because the property was always intended to link to the same type only. This change fixes some violations that were reported by the cm validate-multisite tool.

Follow Section, “Content Types must restrict master links to same type” for upgrade information.

(CMS-13307)

Replication Live Server startup

The configuration option replicator.preventOnlineSwitch and the associated JMX property have been removed. As a replacement, the property replicator.force-online-switch has been added. If false (the default), the Replication Live Server waits for the replication process to catch up with the Master Live Server  before going into online runlevel. If true , the server will go online immediately.

Follow Section, “Replication Live Server startup” for upgrade information.

(CMS-12635)