Broadleaf Microservices
  • v1.0.0-latest-prod

Catalog Services Release Notes for 2.0.3-GA

  • The 2.x versions are Spring Boot 3 compatible.

  • This version includes all changes up to 1.8.15 Release Notes

Requirements

  • JDK 17 is required for Broadleaf release trains 2.0.0-GA, and beyond.

  • This version now requires DataTracking 2.0.3+

New Features & Notable Changes

  • Added attributes field to the CategoryAsset and ProductAsset domains.

  • Added an action to the Admin Product page’s Variant list grid row. There is now an option to view Variants in a popup which is readonly. This is helpful in cases where the Product view is readonly and Variants are not editable.

    • An example of when this might occur is when there is a catalog utilizing reference inheritance.

Automatic support for extensible Indexable entities in SearchServices

  • AbstractProductSingleIndexRequestMessageBuilder and AbstractAncillaryProductSingleIndexRequestMessageBuilder sets the _baseClass attribute on the SingleIndexRequest message.

    • If a client has extended OOB Broadleaf class like JpaProduct, then _class may hold the name of that derived type instead of the OOB Broadleaf class. _baseClass field is intended to capture the 'parent' or 'base' of get_class(), which in many cases will be the OOB Broadleaf class.

    • If set, this becomes relevant in message listener/handler components, as they are typically checking these class fields to determine whether they support processing a message. For example, consider a message with (_class = ClientProduct.class, _baseClass = Product.class), and a ProductHandler that declares support for Product.class. If the handler is configured to check for _baseClass first, then it will automatically accept this message for processing - the benefit here is that the client does not have to extend/override the ProductHandler component itself to explicitly declare support for ClientProduct.class.

Bug Fixes

  • Fixed a JsonPathException thrown upon creation and re-indexing of variant-based products with options due to broken translation entity paths in a migration script.

    • This change impacts MicroservicesDemo-based projects only