Relevant Changes in brXM 15

This page outlines the key changes between brXM 14 and brXM 15.

Major Changes

Java 11 Requirement

brXM 15 requires Java 11. If you deploy to the Bloomreach Cloud (OnDemand 2) hosting platform, the platform automatically detects and uses the correct Java version for your uploaded project distribution.

Wicket 9 Upgrade

brXM 15 uses Apache Wicket version 9, which introduces Content Security Policy (CSP) enforcement. If your project includes customizations that depend on the Wicket framework, review and update them as needed. For more information, see Upgrade to Wicket 9. If your implementation loads third-party resources, you may need to update the CSP configuration.

Removal of Delivery API v0.9

Version 0.9 of the Delivery API is no longer available in brXM 15. If your project uses Delivery API v0.9, migrate to v1.0 before upgrading. The SPA SDKs continue to support v0.9.

Minor Changes

The Relevance module now supports Elasticsearch 8.
brXM 15 has removed culturally insensitive terminology.
Support for the Camunda workflow process management library, previously used by the Projects feature, has been removed.
Support for the Unified UI (with Bloomreach Discovery) is being phased out. The related Essentials plugin has been removed.
PDF generation upon submission of "eforms" is deprecated. If you rely on this functionality, contact Bloomreach Support.
By default, GET requests to HST action URLs are now rejected with HTTP status 405 "Method Not Allowed".
The default visitor cookie/header name in the targeting module has changed from _visitor to visitor.
Groovy Updater Scripts now write log messages to standard log files using the logger org.onehippo.repository.update.UpdaterExecutionReport, except when running with the cargo.run profile (local development). Previously, logs were written to JCR nodes and displayed in the UI.
Several third-party libraries have been upgraded.
Support for HST Enterprise Caching has been removed.