2.2.31. Release 7.5.15

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

Release 7.5.15 contains the following CoreMedia modules:

  • CoreMedia Blueprint

  • 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.9
CoreMedia Project Maven ExtensionPROJEXT1.0.5

Table 2.33. Tooling of CoreMedia DXP 8


CoreMedia CMS Improvements

Changes

Removed Http Cache and Persistent Value Cache

  • The Http Cache component and the value cache of the Persistent Cache (aka PersistentValueCache) have been removed with this release.

API changes

  • Removed deprecated class com.coremedia.cap.persistentcache.ReleasingPersistentCacheKey.

    Removed packages com.coremedia.cap.httpcache, com.coremedia.cap.httpcache.persistent and com.coremedia.cap.persistentcache.valuecache.

Replaced Apache Commons Logging with SLF4J in public API

  • Replaced org.apache.commons.logging.Log with org.slf4j.Logger in

    • protected method getLog of com.coremedia.objectserver.web.links.AbstractLinkScheme
    • protected method getLogger of com.coremedia.cap.persistentcache.proactive.BaseReceiver
    • protected method getLog of com.coremedia.springframework.customizer.BeanCustomizer
    • package-private method setLog of com.coremedia.cap.common.pool.CapSessionPool
    • public methods getLog and setLog of com.coremedia.cap.common.pool.CapSessionPoolImpl
    • protected field log and public method setLog of hox.corem.server.media.ChunkingBlobStore
    • protected method getLog of com.coremedia.watchdog.CodeConverter
    • public static field log of com.coremedia.workflow.common.Common
    • protected static field log of com.coremedia.cap.content.ContentHelper
    • package-private static field log of com.coremedia.cap.content.ContentRepository
    • protected method getLogger of com.coremedia.easyedit.taglib.ContextInfoTag
    • protected method getLogger of com.coremedia.objectserver.web.EntryController
    • protected field log of hox.corem.server.media.FileStore
    • protected method getLogger of com.coremedia.easyedit.taglib.HeadTag
    • protected field log of hox.corem.server.media.LoggingMediaStoreSelector
    • protected method getLogger of com.coremedia.easyedit.taglib.PbeTag
    • package-private field log of com.coremedia.cap.workflow.plugin.PerformersPolicy
    • protected field log of hox.corem.server.media.PostgreSQLBlobStore
    • protected method getLog of com.coremedia.cap.persistentcache.ProcessingCallbackBase
    • protected static field log of com.coremedia.cap.content.publication.PublicationHelper
    • protected method getLog of com.coremedia.objectserver.view.RichtextToHtmlFilterFactory
    • package-private static field log of com.coremedia.cap.user.UserRepository
    • public method getLog of com.coremedia.workflow.WfClient
    • package-private field LOG of com.coremedia.cap.workflow.WorkflowRepository

In addition made protected methods getOut and enableOutVerbose deprecated in com.coremedia.cmdline.AbstractUAPIClient , use new methods getLogger and enableVerboseLogging instead.

SQL Configuration for Content Servers and Workflow Server: sql.store.dbProperties is now optional

  • The property sql.store.dbProperties in CoreMedia component's SQL config files sql.properties is now optional and will be determined from database's metadata. This also affects the deployment properties of the Blueprint.

CoreMedia Studio Improvements

CoreMedia Elastic Social Improvements

API Changes

Minor change for the interface com.coremedia.elastic.social.impl.complaints.ComplaintService

  • The com.coremedia.elastic.social.impl.complaints.ComplaintService now allows to add and remove complaints not only for a com.coremedia.elastic.core.api.models.Model, but to all target types supported by Elastic Social. The lastComplaintDate is only modified when the target is a com.coremedia.elastic.core.api.models.Model.

CoreMedia LiveContext for IBM WebSphere Commerce Improvements

ExternalReferenceResolver changes

  • The prefix for search term external references has changed from "cm-searchTerm:" to "cm-searchterm:". The prefix must always be lower-case now.

    The prefix for segment path external references has not changed but case-variations are not accepted any longer. The prefix "cm-segmentpath:" must always be lower-case now.

    The external reference resolver for search terms has been changed to use the Solr search engine internally to provide better performance. It returns content whose keywords search engine field contains the given search term (or a variation in case). Furthermore, it does not search below the folder Navigation/Fragments/Search Landing Pages anymore but below the navigation segment path <root segment>/livecontext-fragments-hidden-page.

    For more details on ExternalReferenceResolvers, see the [CoreMeda LiveContext for IBM WebSphere Commerce Manual], section "The CoreMedia Include Tag".

CoreMedia Project Improvements

CoreMedia Blueprint Improvements

SQL Configuration for Contentservers and Workflowserver: sql.store.dbProperties is now optional

  • The property sql.store.dbProperties is now optional and will be determined from database metadata. This also affects the deployment properties of the Blueprint: The following properties in the files preconfigure.properties and postconfigure.properties in module packages are no longer required:

    • CMS_DB_PROPERTIES
    • MLS_DB_PROPERTIES
    • RLS_DB_PROPERTIES
    • WFS_DB_PROPERTIES.

    The following properties in the file default-deployment.properties in module packages are no longer required:

    • configure.CMS_DB_PROPERTIES
    • configure.MLS_DB_PROPERTIES
    • configure.RLS_DB_PROPERTIES
    • configure.WFS_DB_PROPERTIES.

    The following deployment token defined in file postconfigure.properties are no longer required:

    • @configure.CMS_DB_PROPERTIES@
    • @configure.MLS_DB_PROPERTIES@
    • @configure.RLS_DB_PROPERTIES@
    • @configure.WFS_DB_PROPERTIES@.

Known Issues

Known Issues

  • CMS-1898: Schemaaccess Broken. Schemaaccess servertool still requires sql.store.dbProperties in file sql.properties despite the fact that this property is obsolete (see above). Reintroduce this property in the servertool's sql.properties file in order to make the schemaaccess servertool run. This issue is fixed in the next release.

Closed JIRA Issues

KeyTypeSummaryStatus
CMS-1834BugPreview Token added to links even when I'm not in the test contextFixed
CMS-1732ChangeCache Search Landing Page ResolvingFixed
CMS-1729TaskEnhance Performance of SLP LookupFixed
CMS-1728TaskDocument SearchTermExternalReferenceResolverFixed
CMS-1726BugExternal Page: Wrong IconFixed
CMS-1674BugWrong icon used for Pages Fixed
CMS-1651BugSearch suggestions don't work in content-led scenarioFixed
CMS-1538FeatureLC2: Studio - Catalog View: Allow sorting categories alphabeticallyFixed
CMS-1526BugPagination For Perfect Chef Search Result PageFixed
CMS-1396BugSearch redirect from PC to WCS throws exceptionFixed
CMS-1293ChangeRemove necessity to configure database typeFixed

Table 2.34. 7.5.15


Prev Up Next
 Home