CoreMedia DXP Release Notes, Version 7.5.44-17
2.2. Improvements and Changes | 2.2.26. Release 7.5.19

The CAE Feeder can now be configured to exclude blobs from indexing based on their MIME-type. The default behavior was not changed and blob values are sent to the search engine regardless of their type.

Use the Spring properties feeder.beanMapping.mimeType.includes and/or feeder.beanMapping.mimeType.excludes to configure comma-separated lists of MIME-types to decide whether Blob values of configured ContentBean properties get indexed.

You may also configure MIME-types for only some ContentBean classes or properties by calling the newly introduced methods setMimeTypeIncludes and/or setMimeTypeExcludes of the classes BeanMappingFeedablePopulator, BeanFeedableMapping and BeanPropertyFeedableElementMapping of package com.coremedia.cap.feeder.bean. See the API documentation for more details.

Added configuration property feeder.contentSelector.includeSubTypes for the CAE Feeder to configure whether documents of sub types of the configured content types are indexed as well. The default value is to include sub types (true) which matches the behaviour of previous versions.

All server-side validators will now be executed with the rights of the connection session instead of the current user's session.

The demo content now contains demo content for Perfect Chef Anniversary categories and content that only exist in separate IBM WebSphere Commerce workspace.

The CoreMedia Adaptive Personalization (p13n) integration in LiveContext has been extracted from the lc extension and moved to lc-p13n. The extension consists of the two modules lc-p13n-cae and lc-p13n-studio.

The Elastic Social (es) integration in LiveContext has been extracted from the es extension and moved to lc-es with different sub modules.

The connection timeout and socket timeout are now configurable for the CoreMedia Fragment Connector running within the WCS. Default value for the connection timeout is 10 seconds. The default for the socket read timeout (the time for an expected CAE response) is 30 seconds. Both values can be set in the web.xml of the WCS application.

When navigating to the Product Detail Page (PDP) of a product that only exists in an IBM WebSphere Commerce Workspace, the shop shows an error "Error 403: You are not authorised to access preview.". The workspace preview context is not correctly established and the SEO URL is not found in IBM WebSphere Commerce. A Problem Management Record (PMR) with IBM is still ongoing (PMR 15292,756,000). As a workaround you can navigate to any other shop page (e.g. PDP of a product that exists in the base schema) before navigating to the PDP of a workspace-only product. Then the preview context is correctly established and SEO links to workspace-only products will work.

Using the add to cart feature of e.g. Product Teasers or Quick Info in Image Maps currently do not update the cart icon in the e-Commerce led scenario (e.g. in AuroraESite). Therefore, the default settings in the demo content sets "shopNow=false" in the local settings of the "LiveContext Fragments Root Page". In the content-led scenario (Perfect Chef) the add to cart works as expected and is enabled by default.