close

Filter

loading table of contents...

Release Notes / Version 12.2406.2

Table Of Contents

CoreMedia Core

Updated postgresql driver

Updated `org.postgresql:postgresql` to `42.7.7`

(CMS-28048)

Third-Party Update: OpenCSV

OpenCSV has been updated to version 5.11.1. This includes an update of transitive dependency commons-beanutils to version 1.11.0 and avoids potential security issue CVE-2025-48734.

(CMS-27955)

Deprecation: Workflow JAR Upload

The feature to upload a JAR file of classes with a workflow process definition has been deprecated and should not be used anymore. This avoids potential problems with storing executable code in the database. With different versions of custom code in the database, it can become hard to track which code is actually used in production, and to detect and fix security issues in all variants of uploaded custom code. Furthermore, in case attackers have gained write access to the database, they could use this feature to execute code in the Workflow Server. If unused, it is therefore recommended to disable the usage of uploaded classes by setting the newly introduced configuration property workflow.server.use-uploaded-jar to false. Required classes should be added to the Workflow Server classpath instead.

The Workflow Server does not automatically remove previously uploaded JAR files from the database, if workflow.server.use-uploaded-jar is set to false. In case of unexpected problems with workflows that still need previously uploaded JAR files, it is possible to enable JAR file usage again by setting the property back to true.

As part of this change, the corresponding options j and -jar of the cm upload tool have been deprecated.

The following Java API methods have been deprecated as well, and should not be used anymore:

  • com.coremedia.cap.workflow.WorkflowRepository#createProcessDefinition(byte[], byte[])

  • com.coremedia.cap.workflow.ProcessDefinition#getProcessClasses()

  • com.coremedia.workflow.WfObjectRepository#createProcess(byte[], byte[])

  • com.coremedia.workflow.WfProcess#getProcessClasses()

(CMS-27951)

Fix Content Feeder Background Issue Feeding

Fixed a bug in the Content Feeder that content issues were not indexed in the background.

(CMS-27868)

Updated Maven dependencies and plugins

Updated several dependency and plugin versions.

The following plugins and dependencies have been updated:

Preceding release for the documented updates is 2406.1.3.

(CMS-27859)

Deprecation: Public API for Custom Proactive Engine Application

Custom Proactive Engine / Persistent Cache applications will not be supported anymore in the next major version CMCC 13 (2512.0.0). Proactive Engine and Persistent Cache are internal technical components of the CAE Feeder. They should not be used in custom applications anymore and may not work as before in future release CMCC 13. Consequently, parts of the public Java API have been deprecated.

The following classes and interfaces have been deprecated now for removal in CMCC 13. There is no known use case to keep that API for customization in the CAE Feeder.

  • com.coremedia.cap.persistentcache.InvalidationEvent

  • com.coremedia.cap.persistentcache.InvalidationListener

  • com.coremedia.cap.persistentcache.ProcessingCallback

  • com.coremedia.cap.persistentcache.ProcessingCallbackBase

  • com.coremedia.cap.persistentcache.example.HelloPersistentCacheKey

  • com.coremedia.cap.persistentcache.example.HelloPersistentCacheKeyFactory

  • com.coremedia.cap.persistentcache.proactive.BaseReceiver

  • com.coremedia.cap.persistentcache.proactive.IllegalStateTransitionException

  • com.coremedia.cap.persistentcache.proactive.KeyManager

  • com.coremedia.cap.persistentcache.proactive.KeyPrefixFilteringReceiver

  • com.coremedia.cap.persistentcache.proactive.Receiver

  • com.coremedia.cap.persistentcache.proactive.TriggerBase

  • com.coremedia.cap.persistentcache.proactive.content.ContentAwarePersistentCacheKeyFactory

  • com.coremedia.cap.persistentcache.proactive.content.ContentBeanEvaluator

  • com.coremedia.cap.persistentcache.proactive.content.ContentEvaluator

  • com.coremedia.cap.persistentcache.proactive.content.ContentPersistentCacheKeyFactory

  • com.coremedia.cap.persistentcache.proactive.content.ContentTrigger

  • com.coremedia.cap.persistentcache.proactive.example.LoggingReceiver

  • com.coremedia.cap.persistentcache.proactive.example.PathContentEvaluator

The following interface of package com.coremedia.cap.persistentcache.proactive.content has been deprecated with replacement:

  • ContentTrigger.ContentCollection - use ContentSelection instead

The following methods of package com.coremedia.cap.persistentcache.proactive.content have been deprecated with replacement:

  • ContentSelector.start(ContentTrigger.ContentCollection) - use method start(ContentSelection) instead.

  • PathAndTypeContentSelector.start(ContentTrigger.ContentCollection) - use method start(ContentSelection) instead.

The methods startEvaluators and stopEvaluators of class com.coremedia.cap.persistentcache.proactive.ProactiveEngineManagement have been deprecated. JMX operations of MBean ProactiveEngine with the same name should not be used anymore. They don't have any effect for the CAE Feeder.

(CMS-27400)

Deprecation: Java API Package com.coremedia.cap.server.search

Interfaces and classes of package com.coremedia.cap.server.search have been deprecated in the Java API and should not be used anymore. This includes the Content Server SearchService interface and some related classes that are listed below. They were introduced long time ago for integrating alternative search engines for the Site Manager. The use case does not exist anymore, because the Site Manager has been removed from the product with CMCC 12. Internally, this interface is still used in the Content Server to implement search functionality for the Unified API. However, the now deprecated interface should not be used anymore to customize the implementation of search functionality. In most cases, applications should rather communicate directly with a search engine anyway, and not use the less flexible and less performant Unified API SearchService abstraction.

Note, that there are multiple SearchService interfaces in different packages of the Java API. This deprecation only affects package com.coremedia.cap.server.search.

The following classes and interfaces have been deprecated:

  • com.coremedia.cap.server.search.SearchContext

  • com.coremedia.cap.server.search.SearchException

  • com.coremedia.cap.server.search.SearchService

  • com.coremedia.cap.server.search.SearchServiceResult

(CMS-25951)

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.