Release Notes / CoreMedia Core

Release Notes / Version 12.2412.0

CoreMedia Core

XML Converter Configuration

Due to a bug, XML converters in the contentserver had to be configured with a duplicate sql.store.convert prefix, like

sql.store.convert.sql.store.convert.MyContentType.myXmlProperty=example.org.MyConverter

Follow Section, “XML Converter Configuration” for upgrade information.

(CMS-26006)

Configurable Site Manager Group Alternatives

A feature previously known as a kind of “fallback” has been matured. This fallback was known to take over, when the “site manager groups” field of a given site was empty.

Follow Section, “Configurable Site Manager Group Alternatives” for upgrade information.

(CMS-25668)

Updated to Spring Boot 3.4 and Spring Framework 6.2

The project has been updated to:

Follow Section, “Updated to Spring Boot 3.4 and Spring Framework 6.2” for upgrade information.

(CMS-25319)

CAE Feeder Limits Feeding of Large Binary Values in AMDocumentAsset

The CAE Feeder does not index binary data from AMDocumentAsset contents anymore, if the byte size is larger than the value configured in property feeder.beanPropertyMaxBytes. The same configuration property was already used previously to restrict feeding of other blob values in the CAE Feeder, and defaults to 5 MB. This change is necessary to avoid running out of memory in case of very large binary values.

Follow Section, “CAE Feeder Limits Feeding of Large Binary Values in AMDocumentAsset” for upgrade information.

(CMS-24694)

Using java.time.Duration in ConfigurationProperties for human-readable Duration Specification

To be able to use human-readable duration configurations such as 1d in favor of 86_400 given as seconds, a bunch of properties got transformed to hold java.time.Duration instead of long or int values denoting milliseconds, for example.

The following is a list of affected properties that benefit from this change:

caas
- commerce.assetsearchservice.cache-seonds
- search.cache
  - seconds
  - querylist-search-cache-for-seconds
- strict-transport-security-header.max-age
cae.sitemap.period-minutes
cap.server
- blob-channel-timeout
- cache
  - group-cache-status-interval
  - resource-cache-status-interval
  - rights-cache-status-interval
  - user-chache-status-interval
- kicense-reload-interval-millis
- session-ping-interval
- termination-timeout-seconds
- unique-db-access-write-interval
elastic.core.event-collection-ttl-sec
publisher
- connection-timeout-seconds
- status-interval
replicator.check-timeout
repository.connect-retry-delay-seconds

solr
- connection-timeout
- socket-timeout
- zookeeper.client-timeout
- zookeeper.connect-timeout
sql
- pool
  - check-timeout
  - open-timeout
  - reaper-interval
  - reaper-timeout
  - validator-interval
  - validator-timeout
- store
  - collector
    blob-preservation-period
    delay
    initial-delay
    start-time
  - sgml-cache-interval-seconds
workflow.server
- session
  - reaper-timeout
  - timeout
- termination-timeout-seconds
- tx.idletimeout
- uapi.session-pool.max-idle-time-ms

The following unused properties were removed:

commerce.hub.data.endpoint.shutdown-timeout-millis
workflow.server.sweep.delay
workflow.uapi.connect-retry-delay-seconds (use repository.connect-retry-delay-seconds instead)

Follow Section, “Using java.time.Duration in ConfigurationProperties for human-readable Duration Specification” for upgrade information.

(CMS-24149)

Removed legacy logging configuration in Workflow-Server

Legacy logging configuration in Workflow-Server has been replaced by standard slf4j class log facilities.

All properties with the prefix workflow.common.log and workflow.server.log have been removed.
Managed JMX attributes like isLogClientActions etc have been removed from WorkflowServerManager.
Class com.coremedia.workflow.common.Common has been deleted.

(CMS-23946)

Removed deprecated class `hox.corem.Corem`

Deprecated class hox.corem.Corem was removed. Use Spring's external configuration instead. If hox.corem.Corem was used and the need to load a properties file programmatically remains, then the following code using Spring utility classes can be used as a replacement:

Follow Section, “Removed deprecated class `hox.corem.Corem`” for upgrade information.

(CMS-23765)

Starting XML Importer in a Docker Container

Examples and documentation have been added to illustrate the start of a CoreMedia XML Importer in a Docker container. As the description of starting the importer as a Tomcat webapp was defunct, it has been removed.

Follow Section, “Starting XML Importer in a Docker Container” for upgrade information.

(CMS-15884)

Search Results

Table Of Contents

Filter