JShell Enhancements

Aligned with the recent enhancements for CMCC v12.2506.0.0 of configuration options (for example, via environment properties but also better support for properties stored in .cm.jshell.properties), the API of the coremedia namespace has been enhanced by two new connect methods:

The former makes the repository.url obsolete, which will then be determined from the outer configuration (like from environment variables or from .cm.jshell.properties). The latter leverages the map-like configuration, that already exists for Cap.connect(...) to be also available in JShell. As always, the benefit of using coremedia.connect(...) over Cap.connect(...) is not only automatic close of the connection when leaving JShell, but also heaving a fully-fledged application context at hand, like accessing the SitesService via coremedia.sites (or short: cm.sites).

(CMS-29030)

Third-Party Update: Apache Tika 3.2.3

Apache Tika has been updated to version 3.2.3. As part of this change, transitive dependencies of Apache Tika have been updated.

Updated dependencies:

If you use these libraries in project code, please check their respective release notes for changes and upgrade information.

(CMS-28582)

Deprecated Content Feeder Configuration Properties

The Content Feeder configuration properties feeder.content.issues.reindex-time-max-percentage and feeder.content.issues.reindex-time-window have been deprecated. They have been replaced by properties feeder.content.background-feed.ISSUES.max-time-percentage and feeder.content.background-feeder-max-time-window, which should be used instead.

(CMS-28465)

Third-Party Update: Apache Tika 3.2.2 and Transitive Dependencies

Apache Tika has been updated to version 3.2.2. As part of this change, transitive dependencies of Apache Tika have been updated.

Updated dependencies:

If you use these libraries in project code, please check their respective release notes for changes and upgrade information.

(CMS-28431)

Plugins can Contribute Document Type Aspects

There is a new Extension Point for Plugins. The content-server Application Plugin of a Plugin Bundle can now contain resources matching the classpath pattern classpath*:framework/doctypes/*/.xml. All these files will be picked up as document type definitions, which can contain new document types as well as document type aspects (see Content Server Manual / 4.2.3 Attaching Properties to Existing Content Types). The extended document type model becomes active on first Content Server start after the Plugin has been added.

Important note: If a Plugin comes with custom document type definitions, once you have activated it and started the Content Server, its database is adjusted accordingly. You must not disable the Plugin afterwards, or Content Server might refuse to start, because the additional document type definitions are missing. In case you want to remove such a Plugin, consult the Content Server Manual about adjusting the database after document type changes.

(CMS-27872)

Updated Project Dependencies

Updated several dependency and plugin versions:

(CMS-27700)

Session Check for Blob Download from Content Server Can Be Disabled

Blob Downloads from Content Servers are verified for a valid login session on each call. With the new configuration option cap.server.blob-download-session-validation, this session validation can be disabled. The default for the option is true, i.e., each download request is verified for a valid login session. If set to false, the session validation for downloads is disabled. This is useful on Replication Live Servers to allow for load-balanced blob download. It must only be set to false if corresponding servers are appropriately secured by firewalls, private networks, or the like. Otherwise, public unsecured read access to blobs could be possible. Blob Uploads are always secured by session validation, regardless of the option’s setting.

(CMS-27698)

MongoDB update to version 8.0

MongoDB has been updated to version 8.0 for the Docker Deployment. Note that an upgrade is only possible from a 7.0.x version. An upgrade from an earlier version needs to be done successively. Please refer to the official MongoDB documentation on how to upgrade: https://www.mongodb.com/docs/manual/release-notes/8.0-upgrade-standalone/ The compatibility changes are described here: https://www.mongodb.com/docs/manual/release-notes/8.0-compatibility/

(CMS-25999)

Add Checkbox To Publication Workflow Window To Include Referenced Updated Content

Previously, only unpublished referenced content items were included in the publication. When the new checkbox is enabled, also referenced content items are included that have been updated since their last publication.

The depth for following such references is limited by Studio Setting publication.maxUpdatedLinksDepthToCompleteChangeSet or Spring property studio.rest.changeset-max-updated-links-recursion-depth.

For more details see the section “Configuring Workflow Validation” / “Publication Settings” in the Studio User Manual.

(CMS-17555)