2.2.43. Release 7.5.3

This chapter contains all changes made in Release 7.5.3 of CoreMedia Digital Experience Platform 8.

Release 7.5.3 contains the following CoreMedia modules:

  • CoreMedia Blueprint

  • CoreMedia Blueprint Base

  • CoreMedia CMS

  • CoreMedia Studio

  • CoreMedia LiveContext for IBM WebSphere Commerce

  • CoreMedia Elastic Social

In addition, CoreMedia DXP 8 uses the following tooling:

ProductKeyVersion
CoreMedia Application Maven Plug-inAPPPLUGIN2.7.4
CoreMedia Project Maven ExtensionPROJEXT1.0.5

Table 2.57. Tooling of CoreMedia DXP 8


CoreMedia CMS Improvements

Changes
  • Apache Tika has been updated to version 1.5.

  • The static field com.coremedia.cmdline.AbstractUAPIClient.options has been removed. As before, the Options object is passed to the methods fillInOptions(Options), which is responsible for extending the set of options.

  • The persistence format of the CoreMedia Studio Control Room has been changed and already persisted instances are lost. You need to remove the MongoDb collection lists in the blueprint_internal_models database (assuming "blueprint" is your project name) when you update from an older 7.5 release.

  • Temporarily dropped support for PBE- and Metadata-taglib. Due to the focus on FreeMarker templates and a required metadata syntax change, support for the aforementioned tag libraries has been dropped.

CoreMedia Studio Improvements

Changes
  • The PreviewPanel does not provide the context variable CURRENT_PREVIEW_SELECTION_VARIABLE_NAME anymore. Use the more generic CURRENT_PREVIEW_METADATA_SELECTION_VARIABLE_NAME instead.

  • The PreviewPanel does now provide the context variable CURRENT_PREVIEW_CONTENT_VARIABLE_NAME holding the currently previewed Content object.

Enhancements
  • Locking mechanism introduced for content items of running 2-Step-Publication workflows.

CoreMedia Blueprint Base Improvements

  • Introducing the new SettingsService, which can be used for both applications, the CoreMedia Studio and the CAE, by using SettingsFinder that are able to fetch settings from various types of target beans, be it Content, ContentBeans or even any third-party types.

CoreMedia Blueprint Improvements

  • The complete code now only uses one way for reading settings: The new SettingsService introduced within the CoreMedia Blueprint Base Modules. This service may now be used for the CAE as well as for the CoreMedia Studio by configuring different SettingsFinder. See the CoreMedia LiveContext for IBM WebSphere Commerce Manual for details on how to use that service for your own projects. The following classes could be removed from the Blueprint:

    • The HasSettings interface and its implementing classes AbstractSettings and SettingsImpl

    • The ContentSettingsService

Closed JIRA Issues

KeyTypeSummaryStatus

Table 2.58. 7.5.3