CoreMedia DXP Release Notes, Version 7.5.45-10
2.2. Improvements and Changes | 2.2.33. Release 7.5.13

CoreMedia Blueprint

CoreMedia CMS

CoreMedia Studio

CoreMedia LiveContext for IBM WebSphere Commerce

CoreMedia Elastic Social

The class com.coremedia.livecontext.fragment.resolver.SegmentPathResolver was changed to not perform a possibly expensive content query anymore to find a CMLinkable by URI segment. Instead it uses a search engine query via the newly introduced SegmentResolver service. To this end, all CMLinkable documents need to be indexed by the CAE Feeder. See section "CAE Feeder and Solr configuration changed to index CMLinkable URL segments" below for more information on necessary CAE Feeder and Solr configuration changes.

Added a new extension point caefeeder for the CAE Feeder application for the CoreMedia Project Maven Extension mechanism. To this end, the Maven module caefeeder-extension-dependencies has been added in modules/extension-config.

The CAE Feeder configuration property feeder.contentSelector.contentTypes was changed to index all documents of type CMLinkable (including subtypes). In earlier releases only the following types were indexed by default: CMArticle, CMAudio, CMDownload, CMGallery, CMPicture, CMTaxonomy and CMVideo.

Furthermore, the CAE Feeder is now configured to set the newly introduced Apache Solr index fields segment and contexts to the URL segment and to the contexts of a CMLinkable, respectively. The new fields have been added to the Apache Solr configuration file schema.xml and to the enum com.coremedia.blueprint.cae.search.SearchConstants.FIELDS

These changes make it possible to query the search engine for a CMLinkable with given URL segment and context. This capability is now available as Spring bean segmentResolver implementing the new interface com.coremedia.blueprint.cae.search.SegmentResolver.

Note that the CAE Feeder needs to be started with an empty index and database to index all CMLinkable documents with the newly introduced index fields.

The installation of the CSS Importer has been moved from the content_management_server recipe to a new css_importer recipe in the coremedia cookbook. Include the css_importer recipe after the content_management_server recipe in any run list to restore the former behavior.

The default recipe of the coremedia cookbook will now set the file handle limit for the coremedia user. Therefore, the ulimit cookbook has been added and the coremedia cookbook now depends on the ulimit cookbook. To configure the limit, a new attribute coremedia.filehandle_limit has been added with a default value of 25000.